Processors, Methods, Systems, and Instructions to Generate Sequences of Integers in which Integers in Consecutive Positions Differ by a Constant Integer Stride and Where a Smallest Integer is Offset from Zero by an Integer Offset

ABSTRACT

A method of an aspect includes receiving an instruction. The instruction indicates an integer stride, indicates an integer offset, and indicates a destination storage location. A result is stored in the destination storage location in response to the instruction. The result includes a sequence of at least four integers in numerical order with a smallest one of the at least four integers differing from zero by the integer offset and with all integers of the sequence in consecutive positions differing by the integer stride. Other methods, apparatus, systems, and instructions are disclosed.

BACKGROUND

1. Field

Embodiments relate to processors. In particular, embodiments relate toprocessors having instruction sets that include instructions that usecontrol indexes.

2. Background Information

Many processors have Single Instruction, Multiple Data (SIMD)architectures. In SIMD architectures, a packed data instruction, vectorinstruction, or SIMD instruction may operate on multiple data elementsor multiple pairs of data elements simultaneously or in parallel. Theprocessor may have parallel execution hardware responsive to the packeddata instruction to perform the multiple operations simultaneously or inparallel.

Multiple data elements may be packed within one register or memorylocation as packed data or vector data. In packed data, the bits of theregister or other storage location may be logically divided into asequence of multiple data elements. For example, a 256-bit wide packeddata register may have four 64-bit wide packed data elements, eight32-bit wide packed data elements, sixteen 16-bit wide packed dataelements, etc. Each of the packed data elements may represent a separateindividual piece of data (e.g., a red, green, blue, or alpha colorcomponent of a pixel, or a real or imaginary component of a complexnumber, etc.) that may be operated upon separately or independently ofthe others.

Some SIMD architectures have instructions to flexibly rearrange packeddata elements within one or more source packed data according to controlindexes. Examples of such instructions are permute instructions andshuffle instructions. The control indexes control how the packed dataelements are rearranged by the instructions.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 is a block diagram of an example embodiment of a processor toprocess instructions useful to generate control indexes.

FIG. 2 is a block flow diagram of an example embodiment of a method ofprocessing an example embodiment of a packed data rearrangement controlindexes generation instruction.

FIG. 3 is a block flow diagram of an example embodiment of a method ofprocessing an example embodiment of a packed data rearrangement controlindexes precursors generation instruction.

FIG. 4 is a block diagram of an example embodiment of an instructionprocessing apparatus to process instructions useful to generate controlindexes.

FIG. 5 is a block flow diagram of an example embodiment of a method ofprocessing an instruction that stores a sequence of at least fournon-negative integers that follow a numerical pattern.

FIG. 6 is a block diagram of an embodiment of an instruction format ofan instruction useful to generate control indexes.

FIG. 7A is a block diagram illustrating that in some embodiments asequence of integers stored by an instruction may have a numericalpattern that is based predominantly or entirely on an opcode of theinstruction.

FIG. 7B is a block diagram illustrating that in some embodiments asequence of integers stored by an instruction may have a numericalpattern that is based partly on an opcode of the instruction and partlyon one or more numerical pattern defining parameters indicated by theinstruction.

FIG. 8 is a block flow diagram of an example embodiment of a method ofprocessing an instruction that stores a sequence of at least fourconsecutive non-negative integers in numerical order.

FIG. 9 is a block diagram illustrating an example embodiment of a packeddata rearrangement operation using packed data rearrangement controlindexes having values of offset consecutive integers in numerical orderto extract unaligned packed data from two aligned packed data to avoidneeding to perform unaligned loads.

FIG. 10 is a block flow diagram of an example embodiment of a method ofprocessing an instruction that stores a sequence of at least fournon-negative integers in numerical order with all integers inconsecutive positions differing by a constant integer stride of at leasttwo.

FIG. 11 is a block flow diagram of an example embodiment of a method ofprocessing an instruction that stores a sequence of at least fournon-negative same parity (e.g., all even or all odd) integers innumerical order.

FIG. 12 is a block diagram illustrating an example embodiment of apacked data rearrangement operation using packed data rearrangementcontrol indexes having values of consecutive even integers in increasingnumerical order to separate real numbers (R) from imaginary numbers(IM).

FIG. 13 is a block flow diagram of an example embodiment of a method ofprocessing an instruction that stores a sequence of at least fourintegers in numerical order, where a smallest of the integers is offsetfrom zero by the offset, and where all of the integers in consecutivepositions differ from one another by the stride.

FIG. 14 is a block flow diagram of an example embodiment of a method ofprocessing a first control indexes precursors generation instruction tostore a sequence of consecutive non-negative integers in numerical orderand a second instruction that applies a stride and an offset to each ofthe integers.

FIG. 15 is a block diagram of a source packed data storing Red GreenBlue Alpha four-tuple data.

FIG. 16 is a block diagram of an example embodiment of a processor thatincludes a read-only memory (ROM) storing one or more sequences ofintegers.

FIG. 17A is a block diagram illustrating a first example embodiment of asuitable format for storing control indexes and control indexesprecursors.

FIG. 17B is a block diagram illustrating a second example embodiment ofa suitable format for storing control indexes and control indexesprecursors.

FIG. 18 is a block diagram of an example embodiment of a suitable set ofpacked data registers.

FIG. 19 is a block diagram of an article of manufacture including amachine-readable storage medium storing an instruction useful togenerate control indexes.

FIG. 20A illustrates an exemplary AVX instruction format including a VEXprefix, real opcode field, Mod R/M byte, SIB byte, displacement field,and IMM8.

FIG. 20B illustrates which fields from FIG. 20A make up a full opcodefield and a base operation field.

FIG. 21A is a block diagram illustrating a generic vector friendlyinstruction format and class A instruction templates thereof accordingto embodiments of the invention.

FIG. 21B is a block diagram illustrating the generic vector friendlyinstruction format and class B instruction templates thereof accordingto embodiments of the invention.

FIG. 22 is a block diagram illustrating an exemplary specific vectorfriendly instruction format according to embodiments of the invention.

FIG. 22B is a block diagram illustrating the fields of the specificvector friendly instruction format that make up the full opcode fieldaccording to one embodiment of the invention.

FIG. 22C is a block diagram illustrating the fields of the specificvector friendly instruction format that make up the register index fieldaccording to one embodiment of the invention.

FIG. 22D is a block diagram illustrating the fields of the specificvector friendly instruction format that make up the augmentationoperation field according to one embodiment of the invention.

FIG. 23 is a block diagram of a register architecture according to oneembodiment of the invention.

FIG. 24A is a block diagram illustrating both an exemplary in-orderpipeline and an exemplary register renaming, out-of-orderissue/execution pipeline according to embodiments of the invention.

FIG. 24B shows processor core including a front end unit coupled to anexecution engine unit, and both are coupled to a memory unit.

FIG. 25A is a block diagram of a single processor core, along with itsconnection to the on-die interconnect network and with its local subsetof the Level 2 (L2) cache, according to embodiments of the invention.

FIG. 25B is an expanded view of part of the processor core in FIG. 25Aaccording to embodiments of the invention.

FIG. 26 is a block diagram of a processor that may have more than onecore, may have an integrated memory controller, and may have integratedgraphics according to embodiments of the invention.

FIG. 27, shown is a block diagram of a system in accordance with oneembodiment of the present invention.

FIG. 28, shown is a block diagram of a first more specific exemplarysystem in accordance with an embodiment of the present invention.

FIG. 29, shown is a block diagram of a second more specific exemplarysystem in accordance with an embodiment of the present invention.

FIG. 30, shown is a block diagram of a SoC in accordance with anembodiment of the present invention.

FIG. 31 is a block diagram contrasting the use of a software instructionconverter to convert binary instructions in a source instruction set tobinary instructions in a target instruction set according to embodimentsof the invention.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth(e.g., specific processors, methods, operations, instructions, numericalpatterns, and data formats). However, it is understood that embodimentsof the invention may be practiced without these specific details. Inother instances, well-known circuits, structures and techniques have notbeen shown in detail in order not to obscure the understanding of thisdescription.

Control indexes for permute instructions and shuffle instructions aretypically built up progressively from scratch by executing a series ofgeneral-purpose instructions that operate on source packed data operandshaving source packed data elements. For example, part of a method ofgenerating the control indexes may include executing a series ofgeneral-purpose packed data arithmetic instructions in order to performa series of packed data arithmetic operations on source packed dataelements to ultimately convert the source packed data elements into thecontrol indexes.

One factor that tends to limit the usefulness of permute and shuffleinstructions, as well as other packed data rearrangement instructions ingeneral, is the number of instructions that typically need to beexecuted in order to generate the permute control indexes, shufflecontrol indexes, or other packed data rearrangement control indexes.Several instructions (e.g., around 4 to 10, or even more) may be neededto generate a set of control indexes. Moreover, the number ofinstructions needed generally tends to increase as the total number ofpacked data elements increases, which tends to be the case over time, asthe bit-width of packed data registers increases.

Executing these instructions tends to be expensive in terms ofprocessing time, processor resource utilization, and power consumption.Moreover, such expense tends to detract from, or diminish, the overallbenefit provided by the packed data rearrangement instructions. In somecases, after the control indexes have been generated and used, thecontrol indexes may be discarded, in which case they may need to beregenerated from scratch if the need arises. In other cases, after thecontrol indexes have been generated and used, the control indexes may bestored in main memory, and then later retrieved from the main memoryover a system bus when they are needed. This may help to avoidgenerating the control indexes from scratch each time they are needed,although retrieving the control indexes from main memory also tends totake a significant amount of time.

Disclosed herein are instructions that are useful to generate controlindexes for other instructions (e.g., permute instructions, shuffleinstructions, other packed data rearrangement instructions, and otherinstructions that use control indexes). Also disclosed are processors toexecute the instructions, methods performed by the processors whenprocessing or executing the instructions, and systems incorporating oneor more processors to process or execute the instructions. The variousprocessors and systems disclosed elsewhere herein are suitable.Advantageously, these instructions, processors, methods, and systems mayhelp to reduce the amount of processing time and/or the number ofinstructions that need to be executed in order to generate the controlindexes.

FIG. 1 is a block diagram of an example embodiment of a processor 100 toprocess instructions useful to generate control indexes. The processormay be any of various complex instruction set computing (CISC)processors, various reduced instruction set computing (RISC) processors,various very long instruction word (VLIW) processors, various hybridsthereof, or other types of processors entirely. In some embodiments, theprocessor may be a general-purpose processor (e.g., a general-purposemicroprocessor), although this is not required. Alternatively, theprocessor may be a special-purpose processor. Examples of suitablespecial-purpose processors include, but are not limited to, networkprocessors, communications processors, cryptographic processors,graphics processors, co-processors, embedded processors, digital signalprocessors (DSPs), and controllers (e.g., microcontrollers), to namejust a few examples.

The processor has an instruction set architecture (USA) 101. The ISArepresents a part of the architecture of the processor related toprogramming. The ISA commonly includes the native instructions,architectural registers, data types, addressing modes, memoryarchitecture, interrupt and exception handling, and external input andoutput (I/O) of the processor. The ISA is distinguished from themicroarchitecture, which generally represents the particular processordesign techniques selected to implement the ISA. Processors withdifferent microarchitectures may share a common ISA.

The ISA includes architecturally-visible or architectural registers(e.g., an architectural register file) 102. The architectural registersrepresent on-processor storage locations. The architectural registersmay also be referred to herein simply as registers. Unless otherwisespecified or clearly apparent, the phrases architectural register,register file, and register are used herein to refer to registers thatare visible to the software and/or programmer (e.g., software-visible)and/or the registers that are specified by general-purposemacroinstructions to identify operands. These registers are contrastedto other non-architectural or non-architecturally visible registers in agiven microarchitecture (e.g., temporary registers used by instructions,reorder buffers, retirement registers, microarchitectural read-onlyregisters used by microinstructions, etc.). The illustratedarchitecturally-visible registers include packed data registers 103.Each of the packed data registers is operable to store packed data,vector data, or SIMD data.

The illustrated ISA includes an instruction set 104 that is supported bythe processor. The instructions of the instruction set representmacroinstructions (e.g., instructions provided to the processor forexecution), as opposed to microinstructions or micro-ops (e.g., thosewhich result from a decoder of the processor decodingmacroinstructions). The processor may include specific or particularlogic (e.g., circuitry potentially with some firmware or software) toexecute the instructions of the instruction set.

The instruction set includes one or more instructions that use controlindexes 105. As mentioned above, in some embodiments these may includeone or more permute instructions, shuffle instructions, or other packeddata rearrangement instructions 106. As another option, as will bediscussed further below, in some embodiments, these may include one ormore gather instructions, or load instructions 107, which are operableto gather or load non-contiguous data from off-processor memory usingthe control indexes.

In accordance with embodiments of the invention, the instruction setalso includes one or more instructions that are each useful to generatethe control indexes 108. In some embodiments, these may include one ormore control indexes generation instructions 109 that are operable togenerate the actual control indexes. Each of the control indexesgeneration instructions may be operable to generate the control indexesentirely within the confines of the execution of a singlemacroinstruction. By contrast, conventionally a series ofgeneral-purpose macroinstructions generally need to be executed in orderto gradually or progressively build up the control indexes from scratch.

In some embodiments, the instructions may include one or more controlindexes precursors generation instructions 110, which do not generatethe actual control indexes, but which generate control indexesprecursors. Each of the control indexes precursors generationinstructions may be operable to generate the control indexes precursorsentirely within the confines of the execution of a singlemacroinstruction. Rather than needing to generate the actual controlindexes from scratch, the control indexes precursors may serve as usefulstarting-point or head-start values that may be efficiently convertedinto the actual control indexes by one or more other instructions.Advantageously, the use of the precursors may allow the actual controlindexes to be generated more quickly and/or with fewer instructions thanif starting from scratch.

The processor also includes execution logic 111. The execution logic isoperable to execute or process the instructions of the instruction set.

FIG. 2 is a block flow diagram of an example embodiment of a method 212of processing an example embodiment of a packed data rearrangementcontrol indexes generation instruction. The packed data rearrangementcontrol indexes generation instruction is received, at block 213. Thereceived instruction specifies or otherwise indicates a firstdestination storage location. In some aspects, the first destinationstorage location may be explicitly specified by bits or one or morefields of an encoding of the instruction. In other aspects, the firstdestination storage location may be implicit to the instruction.

A result is stored in the first destination storage location, inresponse to and/or as a result of the packed data rearrangement controlindexes generation instruction, at block 214. The result includes asequence of at least four non-negative integers representing packed datarearrangement control indexes. The at least four integers typically havea plurality of different values (i.e., they are not all the same integervalue). In various embodiments, the sequence may include at least eight,at least sixteen, at least thirty-two, or at least sixty-fournon-negative integers representing packed data rearrangement controlindexes. The result and/or the sequence of integers may be any of theresults and/or sequences of integers disclosed elsewhere herein. In someembodiments, the result and/or the sequence of the integers may begenerated entirely within the confines of the execution of a singlemacroinstruction (e.g., values of the integers may not depend on anyprevious instructions in the program flow).

To further illustrate certain concepts, and although the invention isnot limited in this respect, reception of a packed data rearrangementinstruction occurs, at block 215. In various aspects, this instructionmay be a permute instruction, a shuffle instruction, or another type ofpacked data rearrangement instruction operable to rearrange dataelements in one or more source packed data according to the packed datarearrangement control indexes. The instruction indicates the packed datarearrangement control indexes (e.g., specifies the first destinationstorage location). The instruction also specifies or otherwise indicatesat least one source packed data having packed data elements andspecifies or otherwise indicates a second destination storage location.

A packed data result is stored in the second destination storagelocation, in response to and/or as a result of the packed datarearrangement instruction, at block 216. The packed data result includesdata elements from the at least one source packed data rearrangedaccording to the packed data rearrangement control indexes. In someembodiments, as in the case of many permute and shuffle instructions,the packed data rearrangement control indexes may identify, select, orotherwise index particular data elements within the at least one sourcepacked data. The indexed data elements may be stored in result dataelements that correspond in position to the indexes.

FIG. 3 is a block flow diagram of an example embodiment of a method 317of processing an example embodiment of a packed data rearrangementcontrol indexes precursors generation instruction. The packed datarearrangement control indexes precursors generation instruction isreceived, at block 318. The received instruction specifies or otherwiseindicates a destination storage location.

A result is stored in the destination storage location, in response toand/or as a result of the packed data rearrangement control indexesprecursors generation instruction, at block 319. The result includes asequence of at least four non-negative integers representing packed datarearrangement control indexes precursors. The at least four integerstypically have a plurality of different values. In various embodiments,the sequence may include at least eight, at least sixteen, at leastthirty-two, or at least sixty-four non-negative integers representingpacked data rearrangement control indexes precursors. The result and/orthe sequence of integers may be any of the results and/or sequences ofintegers disclosed elsewhere herein. In some embodiments, the resultand/or the sequence of the integers may be generated entirely within theconfines of the execution of a single macroinstruction (e.g., values ofthe integers may not depend on any previous instructions in the programflow).

To further illustrate certain concepts, and although the invention isnot limited in this respect, execution of at least one additionalinstruction (e.g., at least one general-purpose arithmetic instruction)is performed to convert the packed data rearrangement control indexesprecursors into packed data rearrangement control indexes, at block 320.A first of the at least one additional instruction may indicate thedestination storage location as a source of the packed datarearrangement control indexes precursors.

Then, a packed data rearrangement instruction indicating the packed datarearrangement control indexes may be executed, at block 321. Theoperation of the packed data rearrangement instruction may be similar tothat previously described.

In FIGS. 2 and 3, the operations at blocks 215, 216, 320, and 321 havebeen shown to better illustrate certain concepts. However, it is to beunderstood that the invention is not limited to the operations performedat these blocks. Other embodiments pertain to methods and operations ofthe individual packed data rearrangement control indexes generationinstructions, and still other embodiments pertain to methods andoperations of the individual packed data rearrangement control indexesprecursors generation instructions, which are not limited to theoperations of other subsequent instructions.

FIG. 4 is a block diagram of an example embodiment of an instructionprocessing apparatus 400. The instruction processing apparatus may be aprocessor, or may be part of a processor. For example, in someembodiments, the instruction processing apparatus may be, or may be partof, the processor 100 of FIG. 1, or one similar. Alternatively, theinstruction processing apparatus may be included in a differentprocessor, or electronic system (e.g., one of the other processors orsystems disclosed herein).

The instruction processing apparatus may receive an instruction 408 thatis useful to generate control indexes. The instruction may represent anyof the various embodiments of the instructions useful to generatecontrol indexes disclosed elsewhere herein. The instruction mayrepresent a machine instruction, macroinstruction, or like controlsignal. The instruction processing apparatus has specific or particularcircuitry or other logic (e.g., hardware potentially combined withfirmware and/or software) that is operable to process the instructionand/or store a result in response to, as a result of, and/or accordingto the instruction.

The illustrated instruction processing apparatus includes an instructiondecoder 422. The decoder may receive and decode higher-level machineinstructions or macroinstructions, and output one or more lower-levelmicro-operations, micro-code entry points, microinstructions, or otherlower-level instructions or control signals that reflect and/or arederived from the original higher-level instruction. The one or morelower-level instructions or control signals may implement the operationof the higher-level instruction through one or more lower-level (e.g.,circuit-level or hardware-level) operations. The decoder may beimplemented using various different mechanisms including, but notlimited to, microcode read only memories (ROMs), look-up tables,hardware implementations, programmable logic arrays (PLAs), and othermechanisms used to implement decoders known in the art.

Alternatively, instead of having the decoder 422, in one or more otherembodiments, the apparatus may have an instruction emulator, translator,morpher, interpreter, or other instruction conversion logic. Variousdifferent types of instruction conversion logic are known in the artsand may be implemented in software, hardware, firmware, or a combinationthereof. The instruction conversion logic may receive the instruction,emulate, translate, morph, interpret, or otherwise convert it into oneor more corresponding derived instructions or control signals. In stillother embodiments, the instruction processing apparatus may have bothinstruction conversion logic and a decoder. For example, the instructionprocessing apparatus may have instruction conversion logic to convertthe received instruction into one or more intermediate instructions, anda decoder to decode the one or more intermediate instructions into oneor more lower-level instructions or control signals executable by nativehardware of the instruction processing apparatus. Some or all of theinstruction conversion logic may be located off-die from the rest of theinstruction processing apparatus, such as on a separate die or in anoff-die memory.

Referring again to FIG. 4, the instruction useful to generate thecontrol indexes 408 explicitly specifies (e.g., through one or morefields), or otherwise indicates (e.g., implicitly indicates), adestination storage location 427. As shown, in some embodiments, thedestination storage location may be within a set of packed dataregisters 403 of the instruction processing apparatus. Alternatively,the destination storage location may be another register or memorylocation. The packed data registers are architecturally-visibleon-processor storage locations that may be implemented in different waysin different microarchitectures, using well known techniques, and arenot limited to any known particular type of circuit. Various differenttypes of registers are suitable as long as they are capable of storingand providing data as described herein. Examples of suitable types ofregisters include, but are not limited to, dedicated physical registers,dynamically allocated physical registers using register renaming, andcombinations thereof.

The instruction processing apparatus also includes an execution unit423. The execution unit is coupled with the decoder 422 and thedestination storage location 427. The execution unit may receive fromthe decoder one or more micro-operations, micro-code entry points,microinstructions, other instructions, or other control signals, whichreflect, or are derived from, the instruction 408. By way of example,the execution unit may include an arithmetic logic unit, a logic unit,an arithmetic unit, a functional unit, or the like. The execution unitmay include specific or particular hardware logic (e.g., integratedcircuitry) potentially with other logic (e.g., software, firmware, or acombination) that is operable to execute the instruction (e.g., executeone or more microinstructions) and/or store a result in response to theinstruction.

The execution unit is operable, in response to the instruction and/or asa result of the instruction 408, to store a result 428 in thedestination storage location 427. As shown, in embodiments, the resultmay include a sequence of at least four integers. In embodiments wherethe instruction 408 is a control indexes generation instruction, each ofthe integers may represent a control index. In embodiments where theinstruction 408 is a control indexes precursors generation instruction,each of the integers may represent a control index precursor.

In some embodiments, the execution unit may include calculation logic424 operable to calculate the sequence of the at least four integers.These may be special-purpose or particular circuits (e.g., to calculatethe integers using a column sweep approach, iteratively calculate theintegers, etc.). In other embodiments, the execution unit may access apre-existing copy of the sequence of the at least four integers 425 froma memory 426 (e.g., a non-architecturally visible read only memory (ROM)that is on-die with the execution unit) responsive to the instruction.See e.g., the discussion of FIG. 16 below. In either of theseembodiments, the sequence of integers is typically not accessed fromoff-die main memory or over a system bus.

In some embodiments, the result may include a sequence of at least four,at least eight, at least sixteen, at least thirty-two, or at leastsixty-four, non-negative integers that follow a numerical pattern. Insome embodiments, the integers that follow the numerical pattern may beconsecutive non-negative integers in numerical order (e.g., 0, 1, 2, 3,4, 5, 6, and 7). In other embodiments, the integers that follow thenumerical pattern may be non-negative integers in numerical order withall integers in consecutive positions differing by a constant integerstride of at least two.

In some embodiments, the stride may be equal to two, and the sequence ofintegers may be a sequence of consecutive same parity integers innumerical order. For example, the consecutive same parity integers maybe consecutive even integers (e.g., 0, 2, 4, 6, 8, 10, 12, and 14), orconsecutive odd integers (e.g., 1, 3, 5, 7, 9, 11, 13, and 15). In otherembodiments, the stride (N) may be greater than two (e.g., the stridemay be 3, 4, 8, 16, etc.), and the sequence of integers may includeconsecutive integer multiples of the stride (e.g., 0, N, 2N, 3N, 4N, 5N,6N, and 7N).

In some embodiments, the instruction may explicitly specify or otherwiseindicate one or more numerical pattern defining parameters (e.g., aninteger offset, a constant integer stride, an integer rotation amount,an integer offset and a constant integer stride, etc.). In someembodiments, the instruction may indicate a positive integer offset (K),and a smallest of the integers may be offset from zero by the integeroffset (e.g., in the case of consecutive integers, K, K+1, K+2, K+3,K+4, K+5, K+6, and K+7). In some embodiments, the instruction mayindicate a positive integer offset (K) and a constant integer stride(N), and the integers may be consecutive integer multiples of the stridethat are offset from zero (e.g., K, N+K, 2N+K, 3N+K, 4N+K, 5N+K, 6N+K,and 7N+K). Alternatively, the result and/or the sequence of the at leastfour integers may be any of the results and/or sequences of at leastfour integers disclosed elsewhere herein for the various embodiments ofthe instructions useful to generate control indexes. In someembodiments, the numerical pattern is based entirely or at leastpredominantly on an opcode, or the opcode and one or more numericalpattern defining parameters, of the instruction, or fixed by the opcode,or the opcode and the one or more numerical pattern defining parameters.It still further embodiments, the sequence of integers need not follow anumerical pattern (e.g., they may be seemingly random).

To avoid obscuring the description, a relatively simple instructionprocessing apparatus 400 has been shown and described. In otherembodiments, the instruction processing apparatus may optionally includeother well-known components, such as, for example, an instruction fetchunit, an instruction scheduling unit, a branch prediction unit,instruction and data caches, instruction and data translation lookasidebuffers, prefetch buffers, microinstruction queues, microinstructionsequencers, bus interface units, second or higher level caches, aretirement unit, a register renaming unit, other components included inprocessors, and various combinations thereof. Embodiments may havemultiple cores, logical processors, or execution engines. An executionunit operable to execute an embodiment of an instruction disclosedherein may be included in at least one, at least two, most, or all ofthe cores, logical processors, or execution engines. It is to beunderstood that there are literally numerous different combinations andconfigurations of components in processors, and that the scope of theinvention is not limited to any particular combination or configuration.

FIG. 5 is a block flow diagram of an example embodiment of a method 530of processing an instruction useful to generate control indexes, whichstores a sequence of at least four non-negative integers that follow anumerical pattern. The instruction is received, at block 531. Theinstruction specifies or otherwise indicates a destination storagelocation.

A result is stored in the destination storage location, in response tothe instruction and/or as a result of the instruction, at block 532. Theresult includes a sequence of at least four non-negative integers thatfollow a numerical pattern. In various embodiments, the result mayinclude a sequence of at least eight, at least sixteen, at leastthirty-two, at least sixty-four, or even more non-negative integers thatfollow the numerical pattern. The sequence of integers may be any of thesequences of integers that follow the various numerical patternsdisclosed elsewhere herein. Often, at least two, at least four, at leasthalf, or even all of the integers may have a different value (i.e., theintegers are typically not all identical).

FIG. 6 is a block diagram of an embodiment of an instruction format foran instruction 608 useful to generate control indexes. The instructionformat includes an opcode 633. The opcode may represent a plurality ofbits or one or more fields of the instruction format to identify theinstruction. The instruction format also includes a destination storagelocation 634. In the illustrated embodiment, the instruction formatincludes a plurality of bits or one or more fields of the instructionformat to explicitly specify the destination storage location.Alternatively, the destination storage location may be implicit to theinstruction.

In some embodiments, the instruction format does not explicitly specify,implicitly indicate, or otherwise indicate, an architecturally-visiblesource storage location (e.g., a packed data register or a main memorylocation) having packed data elements to be operated on by theinstruction 635. In embodiments of the invention, sequences of integers,control indexes, and control indexes precursors, which are stored byinstructions disclosed herein, are not calculated or otherwise derivedfrom packed data elements in an architecturally-visible source storagelocation. By contrast, as discussed in the background section,conventionally permute and shuffle control indexes are typically builtup gradually from scratch by executing a series of general-purposeinstructions (e.g., general-purpose packed data arithmetic instructions)that do operate on packed data elements in architecturally-visiblesource packed data registers until the packed data elements areultimately converted into the permute or shuffle control indexes. Inembodiments of the invention, the sequences of integers, controlindexes, and control indexes precursors, which are stored byinstructions disclosed herein, are generated entirely within theconfines of the execution of the single instruction, and are not basedon results of any preceding instructions in program order.

In some embodiments, the instruction format may have one or more sourceoperands and/or one or more immediates to explicitly specify one or morenumerical pattern defining parameters 636. Alternatively, one or morenumerical pattern defining parameters may be implicitly indicated by theinstruction (e.g., provided through a register implicitly indicated bythe instruction. Each of the one or more pattern defining parameters mayaffect a numerical pattern of a result or sequence of integers stored asa result of the instruction. Each of the one or more pattern definingparameters may affect values of each of the integers in the sequence orresult. Each of the one or more pattern defining parameters may be usedto evaluate a numerical pattern defining equation or relation that isimplicit to the instruction. A few representative examples of suitablenumerical pattern defining parameters include, but are not limited to,integer offsets from zero, integer strides, integer rotation amounts,and combinations thereof (e.g., integer offsets from zero together withinteger strides).

In other embodiments, the instruction may not specify or otherwiseindicate any numerical pattern defining parameters. In some embodiments(e.g., in embodiments where the instruction does not specify orotherwise indicate any numerical pattern defining parameters), theinstruction may not have (e.g., specify or otherwise indicate) anysource operands 637.

FIG. 7A is a block diagram illustrating that in some embodiments asequence of integers 740A in a result 728A stored in a destinationstorage location 727A by an instruction 708A may have a numericalpattern that is based entirely or at least predominantly 738 on anopcode 733A of the instruction. The instruction has the opcode and bitsor one or more fields 734A to specify the destination storage location727A. Note that the instruction of this embodiment does not specify orotherwise indicate any numerical pattern defining parameters, or anysource operands for that matter. Execution of the instruction causes theresult to be stored in the destination storage location. The resultincludes the sequence of integers having the numerical pattern. In theseembodiments, the numerical pattern of the sequence of integers is basedentirely or at least predominantly on the opcode of the instruction. Inthese embodiments, the numerical pattern of the sequence of integers isfixed or constant for the opcode of the instruction. For example, adifference between consecutive integers in the sequence may be basedentirely or at least predominantly on the opcode of the instructionand/or fixed or constant for the opcode of the instruction. Uponidentifying the opcode, the sequence of integers and their numericalpattern may be fixed (i.e., may not depend on any source operands of theinstruction). In some embodiments, the instruction/opcode may only becapable of storing one particular sequence of integers and/or oneparticular numerical pattern. By way of comparison, when general-purposearithmetic instructions operate on source packed data to produce permuteor shuffle control indexes, the permute or shuffle control indexes donot have a numerical pattern that is based entirely or evenpredominantly on the opcode of the general-purpose arithmeticinstructions, rather it is based on the source packed data.

FIG. 7B is a block diagram illustrating that in some embodiments asequence of integers 740B in a result 728B stored in a destinationstorage location 727B by an instruction 708B may have a numericalpattern that is based 739 partly on an opcode 733B of the instructionand partly on one or more numerical pattern defining parameters 736indicated by the instruction. The numerical pattern is based entirely orat least predominantly on the opcode and the one or more numericalpattern defining parameters. The instruction has the opcode, bits or oneor more fields 734B to specify the destination storage location 727B,and specifies or otherwise indicates the one or more numerical patterndefining parameters 736. Execution of the instruction causes the resultto be stored in the destination storage location. The result includesthe sequence of integers having the numerical pattern. In theseembodiments, the numerical pattern of the sequence of integers is basedpartly on the opcode of the instruction and partly on the one or morenumerical pattern defining parameters indicated by the instruction, butis based entirely or at least predominantly on the opcode and the one ormore numerical pattern defining parameters (i.e., is not based on sourcepacked data stored as a result by a preceding instruction).

FIG. 8 is a block flow diagram of an example embodiment of a method 830of processing an instruction useful to generate control indexes, whichstores a sequence of at least four consecutive non-negative integers innumerical order. The instruction is received, at block 831. Theinstruction specifies or otherwise indicates a destination storagelocation.

A result is stored in the destination storage location, in response tothe instruction and/or as a result of the instruction, at block 832. Theresult includes a sequence of at least four consecutive non-negativeintegers in numerical order. In some embodiments, the result may includea sequence of at least eight, at least sixteen, at least thirty-two, atleast sixty-four, or even more, consecutive non-negative integers innumerical order in the destination storage location. In variousembodiments, the sequence of consecutive integers may include any ofthose shown in Tables 1-3.

Table 1 lists example embodiments of sequences of consecutivenon-negative integers in increasing numerical order for differentnumbers of integers.

TABLE 1 NUMBER OF SEQUENCES OF CONSECUTIVE INTEGERS INTEGERS ININCREASING NUMERICAL ORDER 4 0 1, 2, 3 8 0, 1, 2, 3, 4, 5, 6, 7 16 0, 1,2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 32 0, 1, 2, 3, 4, 5, 6,7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25,26, 27, 28, 29, 30, 31 64 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63

In increasing numerical order, the values of the integers increase withincreasing bit significance of the destination storage location (e.g.,the smallest integer is to be stored nearest to the lowest-order bit ofthe register, and the largest integer is to be stored nearest to ahighest-order bit of the register). In each of these examples, thesmallest integer is zero. In some embodiments, an instruction/opcode mayonly be capable of storing a sequent of integers selected from Table 1(i.e., it may not be capable of storing other integers), although thisis not required for other embodiments. Such sequences of consecutiveintegers in increasing numerical order are particularly useful forcontrol indexes precursors, since they may be quickly, efficiently, andversatility, arithmetically or logically converted with one or a fewadditional instructions into a wide range of different sequences ofintegers useful for control indexes.

Table 2 lists example embodiments of sequences of consecutivenon-negative integers in decreasing numerical order for differentnumbers of integers.

TABLE 2 NUMBER OF SEQUENCES OF CONSECUTIVE INTEGERS INTEGERS INDECREASING NUMERICAL ORDER 4 3, 2, 1, 0 8 7, 6, 5, 4, 3, 2, 1, 0 16 15,14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0 32 31, 30, 29, 28, 27,26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9,8, 7, 6, 5, 4, 3, 2, 1, 0 64 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53,52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35,34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17,16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0

In the decreasing numerical order, the values of the integers decreasewith increasing bit significance of the destination storage location. Insome embodiments, an instruction may have one or more bits to indicatewhether or not integers are to be stored in increasing or decreasingnumerical order to allow one instruction/opcode to be used for either.Such sequences of consecutive integers in decreasing numerical order areuseful for mirroring packed data rearrangements. In an example mirroringpacked data rearrangement, data elements in a packed data source are“mirrored” about a center of the packed data source. For example, ahighest-order data element in a source is made a lowest-order dataelement in a result, a next-highest-order data element in the source ismade a next-lowest-order data element in the result, and so on, up tomaking a next-to-lowest-order data element in the source anext-to-highest-order data element in the result, and making alowest-order data element in the source a highest-order data element inthe result.

Table 3 lists example embodiments of sequences of consecutivenon-negative integers in increasing numerical order, which have asmallest integer offset from zero by an integer offset (K), fordifferent numbers of integers.

TABLE 3 INTEGER NUMBER OFFSET OFFSET SEQUENCES OF OF FROM ZEROCONSECUTIVE INTEGERS IN INTEGERS (K) INCREASING NUMERICAL ORDER 4 2 2,3, 4, 5 4 K K, K + 1, K + 2, K + 3 8 5 5, 6, 7, 8, 9, 10, 11, 12 8 K K,K + 1, K + 2, K + 3, K + 4, K + 5, K + 6, K + 7 16 1 1, 2, 3, 4, 5, 6,7, 8, 9, 10, 11, 12, 13, 14, 15, 16 16 K K, K + 1, K + 2, K + 3, K + 4,K + 5, K + 6, K + 7, K + 8, K + 9, K + 10, K + 11, K + 12, K + 13, K +14, K + 15 32 7 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21,22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38 6412  12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28,29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46,47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64,65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75

As shown, a smallest one of the integers may be offset from zero by theoffset and may have a value of the offset. By way of example, theinteger offset (K) may optionally be added to each of the integers ofthe sequences shown in Table 1. Analogous embodiments are contemplatedfor consecutive non-negative integers in decreasing numerical order.Such consecutive non-negative integers in numerical order, which areoffset from zero by a variable positive integer offset (K), are usefulto help extract unaligned packed data from two aligned packed data toavoid needing to perform unaligned loads (see e.g., the discussion ofFIG. 9).

In some embodiments, the instruction may explicitly specify (e.g.,through a source operand or an immediate) or otherwise indicate (e.g.,implicitly indicate a register having) the integer offset (K). Theoffset (K) represents an example embodiment of a pattern definingparameter, which affects the values of each of the integers in thenumerical pattern, and which the numerical pattern is based on.

In some embodiments, a result may include rotated consecutivenon-negative integers in numerical order, which have been rotated by aninteger rotation amount (R). Table 4 lists example embodiments ofsequences of consecutive non-negative integers in increasing numericalorder, which have been rotated by an integer rotation amount (R), fordifferent numbers of integers.

TABLE 4 INTEGER NUMBER ROTATION ROTATED SEQUENCES OF OF AMOUNTCONSECUTIVE INTEGERS IN INTEGERS (R) INCREASING NUMERICAL ORDER 4 3 1,2, 3, 0 8 5 3, 4, 5, 6, 7, 0, 1, 2 16 2 14, 15, 0, 1, 2, 3, 4, 5, 6, 7,8, 9, 10, 11, 12, 13 32 4 28, 29, 30, 31, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9,10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 2764 1 63, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35,36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53,54, 55, 56, 57, 58, 59, 60, 61, 62

As shown, each integer is rotated in the rotation direction, and whenrotated out of one end is rotated into the other end. In someembodiments, the instruction may explicitly specify (e.g., through asource operand or an immediate) or otherwise indicate (e.g., implicitlyindicate a register having) the rotation amount (R). The rotation amount(R) represents an example embodiment of a pattern defining parameter,which affects the values of each of the integers in the numericalpattern, and which the numerical pattern is based on. The integers maybe rotated either to the right or to the left. In some embodiments, theinstruction may also explicitly specify or implicitly indicate arotation direction. Analogous embodiments are contemplated forconsecutive non-negative integers in decreasing numerical order. Suchrotated consecutive integers are useful for rotating packed dataelements. Such rotated consecutive integers are useful for rotatingpacked data elements in sequences smaller than the full vector size.

FIG. 9 is a block diagram illustrating an example embodiment of a packeddata rearrangement operation using packed data rearrangement controlindexes having values of offset consecutive integers in numerical orderto extract unaligned packed data from two aligned packed data to avoidneeding to perform unaligned loads. The operation may be performed inresponse to a packed data rearrangement instruction.

The packed data rearrangement instruction may indicate a first sourcepacked data 942 having eight data elements A₀-A₇, a second source packeddata 943 having eight data elements B₀-B₇, a third source packed data944 having eight packed data elements C₀-C₇, which each include acorresponding one of eight packed data rearrangement control indexesI₀-I₇, and a result packed data 945. By way of example, each of thecontrol indexes I₀-I₇ may be 4-bits wide and may be included in theleast significant 4-bits of the corresponding packed data element C₀-C₇,which may be 8-bits, 16-bits, 32-bits, or 64-bits wide. Otherinstructions may use other numbers of data elements and control indexes.

The result packed data 945 is generated and stored in response to thepacked data rearrangement operation/instruction. In this embodiment,each of the packed data rearrangement control indexes corresponds to aresult data element in a corresponding bit position. Each of the controlindexes is operable to select any one of the sixteen data elements ofthe first and second source packed data (i.e., any one of A₀-A₇ orB₀-B₇) to be stored into the corresponding result data element. Forexample, the first control index I₀ is operable to select any one ofA₀-A₇ or B₀-B₇ to be stored in a first result packed data element of theresult packed data. Four bits are sufficient to uniquely select any oneof the sixteen source data elements. According to one possibleconvention, a control index has a value of 0 to select A₀, 1 to selectA₁, 2 to select A₂, 3 to select A₃, 4 to select A₄, 5 to select A₅, 6 toselect A₆, 7 to select A₇. A control index has a value of 8 to selectB₀, 9 to select B₁, 10 to select B₂, 11 to select B₃, 12 to select B₄,13 to select B₅, 14 to select B₆, and 15 to select B₇.

In this embodiment, the packed data rearrangement control indexes havevalues of offset consecutive integers in numerical order. In particular,the control indexes I₀, I₁, I₂, I₃, I₄, I₅, I₆, I₇, respectively, havethe values 2, 3, 4, 5, 6, 7, 8, and 9. As shown, these control indexesare operable to select A₂, A₃, A₄, A₅, A₆, A₇, B₀, and B₁, for the eightdata elements of the result packed data. The operation with theseindexes merges A₂-A₇ with B₀-B₁. Rather than needing to performunaligned loads to merge A₂-A₇ with B₀-B₁, such merging may be performedwith the use of the offset consecutive integers in numerical order asthe control indexes.

Similarly, it may be readily seen how consecutive integers in decreasingnumerical order may be used to perform mirroring packed data elementrearrangements. Moreover, it may be readily seen how rotated consecutiveintegers may be used to rotate packed data elements.

FIG. 10 is a block flow diagram of an example embodiment of a method1030 of processing an instruction useful to generate control indexes,which stores a sequence of at least four non-negative integers innumerical order with all integers in consecutive positions differing bya constant integer stride of at least two. The instruction is received,at block 1031. The instruction specifies or otherwise indicates adestination storage location.

A result is stored in the destination storage location, in response tothe instruction and/or as a result of the instruction, at block 1032.The result includes a sequence of at least four non-negative integers innumerical order with all integers in consecutive positions differing bya constant integer stride of at least two. In some embodiments, theresult may include a sequence of at least eight, at least sixteen, atleast thirty-two, at least sixty-four, or even more, non-negativeintegers in numerical order with all integers in consecutive positionsdiffering by a constant integer stride of at least two.

The constant stride represents a constant difference between values ofintegers in consecutive positions in the destination storage location.In various embodiments, the stride may be two, three, four, or more.Integers separated by constant strides of two, three, and four areparticularly useful for processing repetitively-arrangedpaired/two-tuple data (e.g., pairs of real and imaginary numbers, orother pairs of data), three-tuple data (e.g., RGB, or other colorcomponent data), and four-tuple data (e.g., RGBA or other colorcomponent plus transparency/opacity data). Even greater strides areuseful for control indexes for gather instructions that gathernon-contiguous data from memory (e.g., from tables or other structureddata arrangements). In some embodiments, the instruction may only becapable of storing a sequence of integers in which consecutive integersdiffer by a constant stride, although other embodiments are not solimited.

FIG. 11 is a block flow diagram of an example embodiment of a method1130 of processing an instruction useful to generate control indexes,which stores a sequence of at least four non-negative same parity (e.g.,all even or all odd) integers in numerical order. The instruction isreceived, at block 1131. The instruction specifies or otherwiseindicates a destination storage location.

A result is stored in the destination storage location, in response tothe instruction and/or as a result of the instruction, at block 1132.The result includes a sequence of at least four non-negative same parityintegers in numerical order. The parity of an integer refers to whetherit is even or odd. Even integers have a same parity, and odd numbershave a same parity, which is a different parity than that of the evennumbers. In some embodiments, the result may include a sequence of atleast eight, at least sixteen, at least thirty-two, at least sixty-four,or even more, even integers (e.g., consecutive even integers) innumerical order. In other embodiments, the result may include a sequenceof at least eight, at least sixteen, at least thirty-two, at leastsixty-four, or even more, odd integers (e.g., consecutive odd integers)in numerical order.

Table 5 lists example embodiments of sequences of consecutive evenintegers in increasing numerical order for different numbers ofintegers.

TABLE 5 NUMBER OF SEQUENCES OF CONSECUTIVE EVEN INTEGERS INTEGERS ININCREASING NUMERICAL ORDER 4 0, 2, 4, 6 8 0, 2, 4, 6, 8, 10, 12, 14 160, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30 32 0, 2, 4, 6,8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42,44, 46, 48, 50, 52, 54, 56, 58, 60, 62 64 0, 2, 4, 6, 8, 10, 12, 14, 16,18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52,54, 56, 58, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88,90, 92, 94, 96, 98, 100, 102, 104, 106, 108, 110, 112, 114, 116, 118,120, 122, 124, 126

Table 6 lists example embodiments of sequences of consecutive oddintegers in increasing numerical order for different numbers ofintegers.

TABLE 6 NUMBER SEQUENCES OF CONSECUTIVE OF ODD INTEGERS IN INCREASINGINTEGERS NUMERICAL ORDER 4 1, 3, 5, 7 8 1, 3, 5, 7, 9, 11, 13, 15 16 1,3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31 32 1, 3, 5, 7, 9,11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41, 43, 45,47, 49, 51, 53, 55, 57, 59, 61, 63 64 1, 3, 5, 7, 9, 11, 13, 15, 17, 19,21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41, 43, 45, 47, 49, 51, 53, 55,57, 59, 61, 63, 65, 67, 69, 71, 73, 75, 77, 79, 81, 83, 85, 87, 89, 91,93, 95, 97, 99, 101, 103, 105, 107, 109, 111, 113, 115, 117, 119, 121,123, 125, 127

In some embodiments, an instruction/opcode may only be capable ofstoring a sequent of integers selected from Tables 5 or 6 (i.e., it maynot be capable of storing other integers), although this is not requiredfor other embodiments. Such sequences of consecutive even and oddintegers are particularly useful for processing repetitively-arrangedtwo-tuple data, such as, for example, pairs of real and imaginarynumbers representing complex numbers, as well as other paired data. Forexample, such sequences of consecutive even and odd integers may be usedto separate, isolate, or de-interleave one type of paired or two-tupledata from another (e.g., separate real numbers from imaginary numbers).See e.g., the discussion of FIG. 12.

In other embodiments, an integer offset (K) may optionally be added toeach of the same parity integers. In still other embodiments, thesequence of same parity integers may be rotated by an integer rotationamount (R). In still further embodiments, the same parity integers maybe in decreasing numerical order.

FIG. 12 is a block diagram illustrating an example embodiment of apacked data rearrangement operation using packed data rearrangementcontrol indexes having values of consecutive even integers in increasingnumerical order to separate real numbers (R) from imaginary numbers(IM). The operation may be performed in response to a packed datarearrangement instruction.

The instruction may indicate a first source packed data 1242 havingeight data elements R₀, IM₀, R₁, IM₁, R₂, IM₂, R₃, IM₃, a second sourcepacked data 1243 having eight data elements R₄, IM₄, R₅, IM₅, R₆, IM₆,R₇, IM₇, a third source packed data 1244 having eight data elementsC₀-C₇, each including a corresponding one of eight packed datarearrangement control indexes I₀-I₇, and a result packed data 1245. Inthe first and second source packed data, real numbers (R) and imaginarynumbers (IM) are interleaved. By way of example, each of the controlindexes I₀-I₇ may be 4-bits wide and may be included in the leastsignificant 4-bits of the corresponding data element C₀-C₇.

The result packed data 1245 is generated and stored in response to thepacked data rearrangement operation/instruction. In this embodiment,each of the control indexes corresponds to a result data element in acorresponding bit position. In this embodiment, the control indexes havevalues of consecutive even integers in increasing numerical order. Inparticular, the control indexes I₀, I₁, I₂, I₃, I₄, I₅, I₆, and I₇,respectively, have the values 0, 2, 4, 6, 8, 10, 12, and 14. As shown,these control indexes are operable to select and store the real numbersR₀, R₁, R₂, R₃, R₄, R₅, R₆, and R₇, in the eight data elements of theresult packed data. This essentially de-interleaves or separates thereal numbers (R) from the imaginary numbers (IM).

In an alternate embodiment, a similar packed data rearrangementoperation may be performed using control indexes having values ofconsecutive odd integers in increasing numerical order to separate theimaginary numbers (I) from the real numbers (R). In particular, thecontrol indexes I₀, I₁, I₂, I₃, I₄, I₅, I₆, and I₇, respectively, mayhave the values 1, 3, 5, 7, 9, 11, 13, and 15, in order to select andstore the imaginary numbers IM₀, IM₁, IM₂, IM₃, IM₄, IM₅, IM₆, and IM₇,in the eight data elements of the result packed data. Moreover, controlindexes having consecutive even or odd integers in numerical order mayalso be used to separate other types of paired or two-tuple data.

In other embodiments, the stride may be greater than two. Table 7 listsexample embodiments of sequences of integers in numerical order, withintegers in consecutive positions differing by a constant integer stridethat is greater than two, for different numbers of integers.

TABLE 7 SEQUENCES OF INTEGERS NUMBER CONSTANT IN INCREASING NUMERICAL OFSTRIDE ORDER DIFFERING BY STRIDE INTEGERS (N) GREATER THAN TWO 4 3 0, 3,6, 9 4 4 0, 4, 8, 12 4 8 0, 8, 16, 24 4 N 0, N, 2N, 3N 8 3 0, 3, 6, 9,12, 15, 18, 21 8 4 0, 4, 8, 12, 16, 20, 24, 28 8 8 0, 8, 16, 24, 32, 40,48, 56 8 N 0, N, 2N, 3N, 4N, 5N, 6N, 7N 16 3 0, 3, 6, 9, 12, 15, 18, 21,24, 27, 30, 33, 36, 39, 42, 45 16 4 0, 4, 8, 12, 16, 20, 24, 28, 32, 36,40, 44, 48, 52, 56, 60 16 8 0, 8, 16, 24, 32, 40, 48, 56, 64, 72, 80,88, 96, 104, 112, 120 16 N 0, N, 2N, 3N, 4N, 5N, 6N, 7N, 8N, 9N, 10N,11N, 12N, 13N, 14N, 15N

These are just a few illustrative examples. For simplicity, examples areonly shown for four, eight, or sixteen control indexes or controlindexes precursors, although other numbers are also contemplated (e.g.,32, 64, etc.). Also, for simplicity, only a few representative examplesof strides are shown (i.e., 3, 4, and 8), although other strides arealso possible (e.g., 5, 6, 10, 16, etc.). Still other embodiments arecontemplated in which the integers of the sequence are in decreasingnumerical order, are offset from zero, and/or are rotated.

FIG. 13 is a block flow diagram of an example embodiment of a method1330 of processing an instruction useful to generate control indexes,which stores a sequence of at least four integers in numerical order,where a smallest of the integers is offset from zero by the offset (K),and where all of the integers in consecutive positions differ from oneanother by the stride (N). The instruction is received, at block 1331.The instruction specifies or otherwise indicates a destination storagelocation.

In some embodiments, the instruction explicitly specifies, or otherwiseindicates, an integer offset (K) and a constant integer stride (N). Insome embodiments, the instruction may have at least one of a sourceoperand and an immediate to explicitly specify the offset (K) and/or thestride (N). As another option, the instruction may implicitly indicate aregister that provides the offset (K) and/or the stride (N). In somecases, the offset may be zero, or in other cases it may be a non-zeropositive integer. The constant integer stride is a positive integer ofone or more. The instruction may set each of the offset (K) and thestride (N) to obtain a desired numerical pattern appropriate for thedesired control indexes.

A result is stored in the destination storage location, in response tothe instruction and/or as a result of the instruction, at block 1332.The result includes a sequence of at least four non-negative integers innumerical order in the destination storage location, where a smallest ofthe integers is offset from zero by the offset (K), and where all of theintegers in consecutive positions differ from one another by the stride(N). The value of an integer at position (i) in the destination storagelocation may be equal to the stride (N) multiplied by the position (i)added to the offset (K).

Mathematically, this may be expressed as integer at position(i)=(N*i+K), where i ranges from zero to one less than the total numberof integers in the sequence (e.g., i is 0 for the first integer, i is 1for the second integer, etc.).

Table 8 lists example embodiments of sequences of integers in numericalorder, where a smallest of the integers differs from zero by the offset(K), and where all of the integers in consecutive positions differ fromone another by the stride (N), for different numbers of integers.

TABLE 8 NUMBER CONSTANT SEQUENCES OF INTEGERS OF STRIDE OFFSET FOLLOWINGFORMULA INTEGERS (N) (K) (N*i + K) 4 2 1 1, 3, 5, 7 4 3 2 2, 5, 8, 11 44 2 2, 6, 10, 14 4 N K K, N + K, 2N + K, 3N + K 8 2 2 2, 4, 6, 8, 10,12, 14, 16 8 3 1 1, 4, 7, 10, 13, 16, 19, 22 8 4 3 3, 7, 11, 15, 19, 23,27, 31 8 N K K, N + K, 2N + K, 3N + K, 4N + K, 5N + K, 6N + K, 7N + K 162 4 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 36 16 3 77, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46, 49, 52 16 4 3 3,7, 11, 15, 19, 23, 27, 31, 35, 39, 43, 47, 51, 55, 59, 63 16 N K K, N +K, 2N + K, 3N + K, 4N + K, 5N + K, 6N + K, 7N + K, 8N + K, 9N + K, 10N +K, 11N + K, 12N + K, 13N + K, 14N + K, 15N + K

As discussed above, consecutive non-negative integers in numerical orderare useful and versatile for generating a variety of different integersequences and/or numerical patterns. In some embodiments, an instructionthat stores consecutive non-negative integers in numerical order may beused together with an instruction that applies a stride and an offset togenerate one of numerous useful numerical patterns.

FIG. 14 is a block flow diagram of an example embodiment of a method1446 of processing a first control indexes precursors generationinstruction to store a sequence of consecutive non-negative integers innumerical order a second instruction that applies a stride and an offsetto each of the consecutive non-negative integers in numerical order.

The first control indexes precursors generation instruction is received,at block 1431. The instruction specifies or otherwise indicates a firstdestination storage location.

A first result is stored in the first destination storage location, inresponse to the first instruction, at block 1432. The result includes asequence of at least four consecutive non-negative integers in numericalorder. In some embodiments, the result may include one of the sequencesof integers shown in Table 1 above.

A second instruction indicating the sequence of the at least fourconsecutive integers in numerical order (e.g., explicitly specifying thefirst destination storage location as a source) is received, at block1447. The second instruction indicates a second destination storagelocation and indicates a stride (N) and an offset (K). In someembodiments, the second instruction may have at least one source operandand/or immediate to explicitly specify the stride and the offset.

A second result is stored in the second destination storage location, inresponse to the second instruction, at block 1448. The second resultincludes a sequence of at least four non-negative integers in numericalorder, where all integers in consecutive positions differ from oneanother by the stride (N), and where a smallest of the integers isoffset from zero by the offset (K). In some embodiments, each of the atleast four consecutive integers may be multiplied by the stride (N), andthe offset (K) may be added to each of the products. For example, thestride (N) may be broadcast into a plurality of values of the stride (N)in a first temporary register, the offset (K) may be broadcast into aplurality of values of the offset (K) in a second temporary register,and each of the at least four consecutive integers may be multiplied bythe first temporary register and the resulting products may be added tothe second temporary register. The sequence of integers of the secondresult may follow the numerical pattern (N*i+K).

FIG. 15 is a block diagram of a source packed data 1542 storing RGBA(i.e., Red Green Blue Alpha) four-tuple data. The RGBA data representscolor component plus transparency/opacity data. RGBA data is commonlyused in computers and other electronic devices having displays/screens.The particular illustrated packed data operand has sixteen dataelements. In the illustration, the sixteen data elements respectivelystore R₀, G₀, B₀, A₀, R₁, G₁, B₁, A₁, R₂, G₂, B₂, A₂, R₃, G₃, B₃, A₃. Insome embodiments, a numerical pattern or sequence of integers may beoperable to perform useful operations on four-tuple data.

Table 9 lists example embodiments of sequences of integers to performvarious useful operations on RGBA data or other 4-tuple data. Many ofthese sequences are useful for four-tuple data in general.

TABLE 9 NUMBER OF SEQUENCES OF INTEGERS INTEGERS EXAMPLE OF USE 16 0, 4,8, 12, 1, 5, 9, 13, 2, 6, Separate each of the R, 10, 14, 3, 7, 11, 15G, B, and A components 16 3, 2, 1, 0, 7, 6, 5, 4, 11, 10, Reverse ormirror order 9, 8, 15, 14, 13, 12 within RGBA four-tuples 16 0, 1, 2, 4,5, 6, 8, 9, 10, 12, Remove A components from 13, 14 RGBA four-tuples 160, 1, 3, 2, 4, 5, 7, 6, 8, 9, Swap order of R and G 11, 10, 12, 13, 15,14 components within RGBA four-tuples 16 3, 0, 1, 2, 7, 4, 5, 6, 11, 8,Convert from RGBA to 9, 10, 15, 12, 13, 14 ARGB 16 2, 1, 0, 3, 6, 5, 4,7, 10, 9, Convert from RGBA to 8, 11, 14, 13, 12, 15 BGRA

Notice that these numerical patterns have a repeat unit of four integerssuch that the pattern repeats every four integers. These are just a fewexamples. Other sequences to perform other operations are alsocontemplated.

Still other embodiments need not utilize packed data rearrangementcontrol indexes with numerical patterns. In general, any sequence ofintegers may be used as long as it is useful for control indexes orcontrol indexes precursors.

The integers may have values appropriate for control indexes or controlindexes precursors. Commonly, packed data rearrangement instructions usecontrol indexes that are operable to index or select any one of 4 sourcepacked data elements, 8 source packed data elements, 16 source packeddata elements, 32 source packed data elements, 64 source packed dataelements, or in some cases 128 source packed data elements. Inembodiments, each of the integers in a sequence may have a value thatranges from zero to an upper bound that is one less than the totalnumber of data elements that the associated packed data rearrangementinstruction indexes among.

For example, in various embodiments, the integer values may all rangefrom 0 to 127 in order to index or select any one of 128 source packeddata elements, may range from 0 to 63 in order to index any one of 64data elements, may range from 0 to 31 in order to index any one of 32data elements, may range from 0 to 15 in order to index any one of 16data elements, or may range from 0 to 7 in order to index any one of 8data elements. In some embodiments, the instruction/opcode may beincapable of storing integers outside of these ranges, although this isnot required for other embodiments. Instructions useful to generatecontrol indexes for gather or load instructions that load non-contiguousdata from memory (e.g., from a table) often have somewhat greater rangesof integer values.

Various ISAs have one or more instructions that load data fromnon-contiguous memory locations or store data to non-contiguous memorylocations. Examples of such instructions include, but are not limited togather and scatter instructions. By way of example, the gatherinstructions may gather or load multiple data elements into a resultpacked data from multiple non-contiguous memory locations using a gatherindex vector provided through a source of the gather instructions. Thescatter instructions may scatter or store multiple data elements from asource packed data into multiple non-contiguous memory locations using ascatter index vector provided through a source of the scatterinstructions. In some embodiments, the control indexes generationinstructions disclosed herein may be used to generate control indexesfor such gather and/or scatter instructions and/or for otherinstructions that access non-contiguous locations in memory. Forexample, the control indexes generation instructions disclosed hereinmay be used to generate gather index vectors and/or scatter indexvectors that may be indicated as source operands, respectively, by thegather or scatter instructions.

Gather and scatter instructions are useful for various differentpurposes. In some embodiments, the gather and scatter instructions areused, respectively, to load data from or store data to, tables or otherregularly arranged data structures. As an example, the gather andscatter instructions may be used to access a row of a two-dimensionalarray when the data is ordered in column-major order. As anotherexample, the gather and scatter instructions may be used to access acolumn of the array when the data is stored in row-major order. Otherexamples include accessing data in multi-dimensional arrays. In suchexamples, sequences or control indexes as disclosed herein may be usedto generate, or assist with generating, the gather index vectors and/orscatter index vectors. Commonly, as in accessing data from a row incolumn-major ordered arrays, or as in accessing data from a column in arow-major ordered array, a constant stride as disclosed elsewhere hereinmay be used. Stride values and offset values as disclosed herein may beused as previously described to generate the gather index vectors and/orscatter index vectors. By way of example, the stride may be based on therow length and/or the column location within the row. The gather orscatter instruction may then specify the gather index vectors and/orscatter index vectors as a source.

Alternatively, in other embodiments, an instruction to load data fromnon-contiguous memory locations (e.g., a gather instruction) or aninstruction to store data to non-contiguous memory locations (e.g., ascatter instruction) may incorporate control indexes generationcapabilities as described elsewhere herein. For example, in someembodiments, a gather instruction and/or a scatter instruction mayindicate a source having one or more of a stride and an offset and thegather and/or scatter instruction may be operable to both use the strideand/or the offset to generate control indexes and perform the gatherand/or scatter operations within the confines of the execution of thesingle gather and/or scatter instruction. The different possibilitiesfor using the stride and the offset mentioned before may also be used bythese instructions. On possible advantage of such instructions is that avector scale-index-base (SIB) may not be needed which may allowreclaiming the traditional SIB and/or a shorter instruction encoding.

Different ways of generating control indexes and/or control indexesprecursors are contemplated. In some embodiments, a sequence of integersmay be stored in a memory of a processor at a time of manufacture (e.g.,prior to runtime execution of application code), and instructions asdisclosed herein (e.g., included in application code at runtime) may beoperable to access the sequence of integers from the memory when theyare executed at runtime.

FIG. 16 is a block diagram of an example embodiment of a processor 1600.The processor includes decode and execution units 1623, packed dataregisters 1603, and a read-only memory (ROM) 1650. The ROM has multiplenon-architecturally visible storage locations 1651. Each of the storagelocations stores a different sequence of integers. For example, a firststorage location 1651-1 stores a first sequence of integers (e.g., 0, 1,2, 3, 4, 5, 6, and 7), an Mth storage location 1651-M stores an Mthsequence of integers (e.g., 0, 2, 4, 6, 8, 10, 12, and 14), and an Nthstorage location 1651-N stores an Nth sequence of integers (e.g., 1, 3,5, 7, 9, 11, 13, and 15). The sequences of integers stored in thesestorage locations represent predetermined sequences of integers. Thestorage locations may store any of the sequences of integers disclosedherein, as well as other sequences entirely. Typically, one or several(e.g., from about two to about ten or more) of the more commonly usedsequences of integers and/or sequences of integers that are relativelymore expensive to generate from scratch may be stored.

The decode and execution units 1623 receive an instruction 1608 that isuseful to generate control indexes. The instruction indicates adestination storage location 1627, which in some embodiments may be inthe packed data registers 1603. In some embodiments, the instruction(e.g., an opcode of the instruction) may implicitly indicate the ROM andthe instruction may indicate one of the non-architecturally visiblestorage locations. In some such embodiments, the one indicatednon-architecturally visible storage location may be fixed or implicit tothe instruction (e.g., fixed or implicit to an opcode of theinstruction). In other such embodiments, the instruction may have one ormore bits to explicitly specify or select the one non-architecturallyvisible storage location. For example, in some embodiments, theinstruction may have one, two, three, four, or more bits, respectively,to select among two, four, eight, or sixteen different predeterminedsequences of integers. Advantageously, in this way oneinstruction/opcode may be capable of selecting among multiple sequencesof integers.

In the illustrated example, the instruction indicates the Mthnon-architecturally visible storage location 1651-M. Responsive to theinstruction, the execution unit may access the Mth sequence of integers(e.g., 0, 2, 4, 6, 8, 10, 12, and 14), and store them in the destinationstorage location 1627. In such embodiments, the Mth sequence of integersdoes not need to be generated or calculated, but ratherpre-existing/pre-stored values may merely be accessed from the ROM. Thismay allow the sequence of integers to be provided quickly andefficiently, within the execution of a single instruction. In someembodiments, the ROM may be on-die with the processor and/or the decodeand execution units, such that the sequence of integers does not need tobe accessed from an off-die main memory or other source and/or over asystem bus.

Processors commonly include ROM on-die to store various different typesof information (e.g., processor identification information,cryptographic keys, configuration information, etc.). There is oftenroom available in such ROM to store one or more sequence of integers asdisclosed herein. Alternatively, a dedicated ROM, a read-only register,a non-architecturally visible register, or another non-architecturallyvisible storage space may be included on-die to store one or moresequence of integers as disclosed herein. As another option, one or moresequences of integers may be burnt into one-time-programmable fuses of aprocessor or otherwise pre-stored or pre-provided on-die with aprocessor and/or execution unit.

In some embodiments, a column-sweep approach may be used to generate anumerical pattern of integers in numerical order. For example, togenerate consecutive integers, a value of 1 may be broadcast across nineelements to give (A). Then, a copy of the elements with the broadcastedvalues of 1 may be shifted to the left to give (B). Then (A) and (B) maybe added to give (C). Then (C) may be shifted to the left by two to give(D). Then (C) and (D) may be added to give (E). Then (E) may be shiftedleft by four to give (F). Then (E) and (F) may be added to give (G),etc.

1 1 1 1 1 1 1 1 1 (A)

1 1 1 1 1 1 1 1 (B)

2 2 2 2 2 2 2 2 1 (C)

2 2 2 2 2 2 1 (D)

4 4 4 4 4 4 3 2 1 (E)

4 4 3 2 1 (F)

8 8 7 6 5 4 3 2 1 (G)

Such column-sweep approaches generally allow for generation of thesequences of integers quickly, as compared to purely iterativegeneration. In still other embodiments, a sequence of integers asdisclosed herein may be generated iteratively. For example to generateconsecutive integers, each integer may be calculated in turn as theprevious integer calculated plus one.

FIG. 17A is a block diagram illustrating a first example embodiment of asuitable format for storing control indexes and control indexesprecursors. A packed data operand 1742A includes packed data elementsA₀-A_(N). By way of example, there may be 4, 8, 16, 32, or 64, dataelements. Each of the data elements A₀-A_(N) has a differentcorresponding control index or control index precursor. In particular, afirst data element A₀ has a first control index or precursor I₀, asecond data element A₁ has a second control index or precursor I₁, anNth data element A_(N) has an Nth control index or precursor I_(N), etc.Each of the control indexes or precursors is stored in a subset of bitsof the corresponding data element. For example, each of the controlindexes or precursors may be stored in a subset of bits of a lowestorder byte or control byte of the corresponding data element, althoughthis is not required. In various embodiments, each of the controlindexes or precursors may be contained within the lowest order 2-bits,3-bits, 4-bits, 5-bits, or 6-bits, for example, of the correspondingdata element. Each of the control indexes or precursors may be aninteger often having a value ranging from 0 to 64. For packed datarearrangement control indexes/precursors, the maximum integer size, andthe number of bits per control index/precursor, depends on the number ofsource data elements indexed among. In various embodiments, the dataelements may be 8-bit bytes, 16-bit words, 32-bit doublewords, or 64-bitquadwords.

FIG. 17B is a block diagram illustrating a second example embodiment ofa suitable format for storing control indexes and control indexesprecursors. A packed data operand 1742B includes data elements A₀-A_(N).Instead of each of the data elements A₀-A_(N) having a differentcorresponding control index or precursor, the control indexes orprecursors are grouped together contiguously within a subset of dataelements of the packed data operand. In the illustrated embodiment, afirst data element A₀ has a first control index or precursor I₀, asecond control index or precursor I₁, and an Nth control index orprecursor I_(N), etc. Depending upon the size of the control indexes orprecursors, and the size of the data elements, a subset of two or moredata elements may be used to store all of the control indexes orprecursors. Also, in the case of control indexes precursors, they may bestored in a general-purpose or integer register and later converted intopacked data format by a subsequent instruction.

FIG. 18 is a block diagram of an example embodiment of a suitable set ofpacked data registers 1803 suitable for storing packed data operands.The illustrated packed data registers include thirty-two 512-bit widepacked data or vector registers. These thirty-two 512-bit wide registersare labeled ZMM0 through ZMM31. In the illustrated embodiment, the lowerorder 256-bits of the lower sixteen of these registers, namelyZMM0-ZMM15, are aliased or overlaid on respective 256-bit wide packeddata or vector registers labeled YMM0-YMM15, although this is notrequired. Likewise, in the illustrated embodiment, the lower order128-bits of YMM0-YMM15 are aliased or overlaid on respective 128-bitpacked data or vector registers labeled XMM0-XMM1, although this also isnot required. The 512-bit wide registers ZMM0 through ZMM31 are operableto hold 512-bit packed data, 256-bit packed data, or 128-bit packeddata. The 256-bit wide registers YMM0-YMM15 are operable to hold 256-bitpacked data, or 128-bit packed data. The 128-bit wide registersXMM0-XMM1 are operable to hold 128-bit packed data. Each of theregisters may be used to store either packed floating-point data orpacked integer data. Different data element sizes are supportedincluding at least 8-bit byte data, 16-bit word data, 32-bit doublewordor single precision floating point data, and 64-bit quadword or doubleprecision floating point data. Alternate embodiments of packed dataregisters may include different numbers of registers, different sizes ofregisters, and may or may not alias larger registers on smallerregisters.

FIG. 19 is a block diagram of an article of manufacture (e.g., acomputer program product) 1952 including a machine-readable storagemedium 1953. In some embodiments, the machine-readable storage mediummay be a tangible and/or non-transitory machine-readable storage medium.In various example embodiments, the machine-readable storage medium mayinclude a floppy diskette, an optical disk, a CD-ROM, a magnetic disk, amagneto-optical disk, a read only memory (ROM), a programmable ROM(PROM), an erasable-and-programmable ROM (EPROM), anelectrically-erasable-and-programmable ROM (EEPROM), a random accessmemory (RAM), a static-RAM (SRAM), a dynamic-RAM (DRAM), a Flash memory,a phase-change memory, a semiconductor memory, other types of memory, ora combinations thereof. In some embodiments, the medium may include oneor more solid data storage materials, such as, for example, asemiconductor data storage material, a phase-change data storagematerial, a magnetic data storage material, an optically transparentsolid data storage material, etc.

The machine-readable storage medium stores one or more instructionsuseful to generate control indexes 1908. In some embodiments, these mayinclude one or more control indexes generation instructions 1910. Insome embodiments, these may include one or more control indexesprecursors generation instructions 1911. Each of the instructions usefulto generate the control indexes, if executed by a machine, is operableto cause the machine to store a result in a destination storage locationindicated by the instruction. The result includes a sequence of integersrepresenting control indexes or control indexes precursors. Any of theinstructions, results, and sequences of integers disclosed herein, aresuitable. Moreover, other instructions may be stored on the medium(e.g., packed data rearrangement instructions, gather instructions,other instructions that use the control indexes, etc.).

Examples of different types of machines include, but are not limited to,processors (e.g., general-purpose processors and special-purposeprocessors), instruction processing apparatus, and various electronicdevices having one or more processors or instruction processingapparatus. A few representative examples of such electronic devicesinclude, but are not limited to, computer systems, desktops, laptops,notebooks, servers, network routers, network switches, nettops, set-topboxes, cellular phones, video game controllers, etc.

An instruction set includes one or more instruction formats. A giveninstruction format defines various fields (number of bits, location ofbits) to specify, among other things, the operation to be performed(opcode) and the operand(s) on which that operation is to be performed.Some instruction formats are further broken down though the definitionof instruction templates (or subformats). For example, the instructiontemplates of a given instruction format may be defined to have differentsubsets of the instruction format's fields (the included fields aretypically in the same order, but at least some have different bitpositions because there are less fields included) and/or defined to havea given field interpreted differently. Thus, each instruction of an ISAis expressed using a given instruction format (and, if defined, in agiven one of the instruction templates of that instruction format) andincludes fields for specifying the operation and the operands. Forexample, an exemplary ADD instruction has a specific opcode and aninstruction format that includes an opcode field to specify that opcodeand operand fields to select operands (source1/destination and source2);and an occurrence of this ADD instruction in an instruction stream willhave specific contents in the operand fields that select specificoperands. A set of SIMD extensions referred to the Advanced VectorExtensions (AVX) (AVX1 and AVX2) and using the Vector Extensions (VEX)coding scheme, has been, has been released and/or published (e.g., seeIntel® 64 and IA-32 Architectures Software Developers Manual, October2011; and see Intel® Advanced Vector Extensions Programming Reference,June 2011).

Exemplary Instruction Formats

Embodiments of the instruction(s) described herein may be embodied indifferent formats. Additionally, exemplary systems, architectures, andpipelines are detailed below. Embodiments of the instruction(s) may beexecuted on such systems, architectures, and pipelines, but are notlimited to those detailed.

VEX Instruction Format

VEX encoding allows instructions to have more than two operands, andallows SIMD vector registers to be longer than 128 bits. The use of aVEX prefix provides for three-operand (or more) syntax. For example,previous two-operand instructions performed operations such as A=A+B,which overwrites a source operand. The use of a VEX prefix enablesoperands to perform nondestructive operations such as A=B+C.

FIG. 20A illustrates an exemplary AVX instruction format including a VEXprefix 2002, real opcode field 2030, Mod R/M byte 2040, SIB byte 2050,displacement field 2062, and IMM8 2072. FIG. 20B illustrates whichfields from FIG. 20A make up a full opcode field 2074 and a baseoperation field 2042. FIG. 20C illustrates which fields from FIG. 20Amake up a register index field 2044.

VEX Prefix (Bytes 0-2) 2002 is encoded in a three-byte form. The firstbyte is the Format Field 2040 (VEX Byte 0, bits [7:0]), which containsan explicit C4 byte value (the unique value used for distinguishing theC4 instruction format). The second-third bytes (VEX Bytes 1-2) include anumber of bit fields providing specific capability. Specifically, REXfield 2005 (VEX Byte 1, bits [7-5]) consists of a VEX.R bit field (VEXByte 1, bit [7]—R), VEX.X bit field (VEX byte 1, bit [6]—X), and VEX.Bbit field (VEX byte 1, bit[5]—B). Other fields of the instructionsencode the lower three bits of the register indexes as is known in theart (rrr, xxx, and bbb), so that Rrrr, Xxxx, and Bbbb may be formed byadding VEX.R, VEX.X, and VEX.B. Opcode map field 2015 (VEX byte 1, bits[4:0]—mmmmm) includes content to encode an implied leading opcode byte.W Field 2064 (VEX byte 2, bit [7]—W)— is represented by the notationVEX.W, and provides different functions depending on the instruction.The role of VEX.vvvv 2020 (VEX Byte 2, bits [6:3]-vvvv) may include thefollowing: 1) VEX.vvvv encodes the first source register operand,specified in inverted (1s complement) form and is valid for instructionswith 2 or more source operands; 2) VEX.vvvv encodes the destinationregister operand, specified in is complement form for certain vectorshifts; or 3) VEX.vvvv does not encode any operand, the field isreserved and should contain 1111b. If VEX.L 2068 Size field (VEX byte 2,bit [2]-L)=0, it indicates 128 bit vector; if VEX.L=1, it indicates 256bit vector. Prefix encoding field 2025 (VEX byte 2, bits [1:0]—pp)provides additional bits for the base operation field.

Real Opcode Field 2030 (Byte 3) is also known as the opcode byte. Partof the opcode is specified in this field.

MOD R/M Field 2040 (Byte 4) includes MOD field 2042 (bits [7-6]), Regfield 2044 (bits [5-3]), and R/M field 2046 (bits [2-0]). The role ofReg field 2044 may include the following: encoding either thedestination register operand or a source register operand (the rrr ofRrrr), or be treated as an opcode extension and not used to encode anyinstruction operand. The role of R/M field 2046 may include thefollowing: encoding the instruction operand that references a memoryaddress, or encoding either the destination register operand or a sourceregister operand.

Scale, Index, Base (SIB)—The content of Scale field 2050 (Byte 5)includes SS2052 (bits [7-6]), which is used for memory addressgeneration. The contents of SIB.xxx 2054 (bits [5-3]) and SIB.bbb 2056(bits [2-0]) have been previously referred to with regard to theregister indexes Xxxx and Bbbb.

The Displacement Field 2062 and the immediate field (IMM8) 2072 containaddress data.

Generic Vector Friendly Instruction Format

A vector friendly instruction format is an instruction format that issuited for vector instructions (e.g., there are certain fields specificto vector operations). While embodiments are described in which bothvector and scalar operations are supported through the vector friendlyinstruction format, alternative embodiments use only vector operationsthe vector friendly instruction format.

FIGS. 21A-21B are block diagrams illustrating a generic vector friendlyinstruction format and instruction templates thereof according toembodiments of the invention. FIG. 21A is a block diagram illustrating ageneric vector friendly instruction format and class A instructiontemplates thereof according to embodiments of the invention; while FIG.21B is a block diagram illustrating the generic vector friendlyinstruction format and class B instruction templates thereof accordingto embodiments of the invention. Specifically, a generic vector friendlyinstruction format 2100 for which are defined class A and class Binstruction templates, both of which include no memory access 2105instruction templates and memory access 2120 instruction templates. Theterm generic in the context of the vector friendly instruction formatrefers to the instruction format not being tied to any specificinstruction set.

While embodiments of the invention will be described in which the vectorfriendly instruction format supports the following: a 64 byte vectoroperand length (or size) with 32 bit (4 byte) or 64 bit (8 byte) dataelement widths (or sizes) (and thus, a 64 byte vector consists of either16 doubleword-size elements or alternatively, 8 quadword-size elements);a 64 byte vector operand length (or size) with 16 bit (2 byte) or 8 bit(1 byte) data element widths (or sizes); a 32 byte vector operand length(or size) with 32 bit (4 byte), 64 bit (8 byte), 16 bit (2 byte), or 8bit (1 byte) data element widths (or sizes); and a 16 byte vectoroperand length (or size) with 32 bit (4 byte), 64 bit (8 byte), 16 bit(2 byte), or 8 bit (1 byte) data element widths (or sizes); alternativeembodiments may support more, less and/or different vector operand sizes(e.g., 256 byte vector operands) with more, less, or different dataelement widths (e.g., 128 bit (16 byte) data element widths).

The class A instruction templates in FIG. 21A include: 1) within the nomemory access 2105 instruction templates there is shown a no memoryaccess, full round control type operation 2110 instruction template anda no memory access, data transform type operation 2115 instructiontemplate; and 2) within the memory access 2120 instruction templatesthere is shown a memory access, temporal 2125 instruction template and amemory access, non-temporal 2130 instruction template. The class Binstruction templates in FIG. 21B include: 1) within the no memoryaccess 2105 instruction templates there is shown a no memory access,write mask control, partial round control type operation 2112instruction template and a no memory access, write mask control, vsizetype operation 2117 instruction template; and 2) within the memoryaccess 2120 instruction templates there is shown a memory access, writemask control 2127 instruction template.

The generic vector friendly instruction format 2100 includes thefollowing fields listed below in the order illustrated in FIGS. 21A-21B.

Format field 2140—a specific value (an instruction format identifiervalue) in this field uniquely identifies the vector friendly instructionformat, and thus occurrences of instructions in the vector friendlyinstruction format in instruction streams. As such, this field isoptional in the sense that it is not needed for an instruction set thathas only the generic vector friendly instruction format.

Base operation field 2142—its content distinguishes different baseoperations.

Register index field 2144—its content, directly or through addressgeneration, specifies the locations of the source and destinationoperands, be they in registers or in memory. These include a sufficientnumber of bits to select N registers from a PxQ (e.g. 32x512, 16x128,32x1024, 64x1024) register file. While in one embodiment N may be up tothree sources and one destination register, alternative embodiments maysupport more or less sources and destination registers (e.g., maysupport up to two sources where one of these sources also acts as thedestination, may support up to three sources where one of these sourcesalso acts as the destination, may support up to two sources and onedestination).

Modifier field 2146—its content distinguishes occurrences ofinstructions in the generic vector instruction format that specifymemory access from those that do not; that is, between no memory access2105 instruction templates and memory access 2120 instruction templates.Memory access operations read and/or write to the memory hierarchy (insome cases specifying the source and/or destination addresses usingvalues in registers), while non-memory access operations do not (e.g.,the source and destinations are registers). While in one embodiment thisfield also selects between three different ways to perform memoryaddress calculations, alternative embodiments may support more, less, ordifferent ways to perform memory address calculations.

Augmentation operation field 2150—its content distinguishes which one ofa variety of different operations to be performed in addition to thebase operation. This field is context specific. In one embodiment of theinvention, this field is divided into a class field 2168, an alpha field2152, and a beta field 2154. The augmentation operation field 2150allows common groups of operations to be performed in a singleinstruction rather than 2, 3, or 4 instructions.

Scale field 2160—its content allows for the scaling of the index field'scontent for memory address generation (e.g., for address generation thatuses 2^(scale)*index+base).

Displacement Field 2162A—its content is used as part of memory addressgeneration (e.g., for address generation that uses2^(scale)*index+base+displacement).

Displacement Factor Field 2162B (note that the juxtaposition ofdisplacement field 2162A directly over displacement factor field 2162Bindicates one or the other is used)—its content is used as part ofaddress generation; it specifies a displacement factor that is to bescaled by the size of a memory access (N)—where N is the number of bytesin the memory access (e.g., for address generation that uses2^(scale)*index+base+scaled displacement). Redundant low-order bits areignored and hence, the displacement factor field's content is multipliedby the memory operands total size (N) in order to generate the finaldisplacement to be used in calculating an effective address. The valueof N is determined by the processor hardware at runtime based on thefull opcode field 2174 (described later herein) and the datamanipulation field 2154C. The displacement field 2162A and thedisplacement factor field 2162B are optional in the sense that they arenot used for the no memory access 2105 instruction templates and/ordifferent embodiments may implement only one or none of the two.

Data element width field 2164—its content distinguishes which one of anumber of data element widths is to be used (in some embodiments for allinstructions; in other embodiments for only some of the instructions).This field is optional in the sense that it is not needed if only onedata element width is supported and/or data element widths are supportedusing some aspect of the opcodes.

Write mask field 2170—its content controls, on a per data elementposition basis, whether that data element position in the destinationvector operand reflects the result of the base operation andaugmentation operation. Class A instruction templates supportmerging-writemasking, while class B instruction templates support bothmerging- and zeroing-writemasking. When merging, vector masks allow anyset of elements in the destination to be protected from updates duringthe execution of any operation (specified by the base operation and theaugmentation operation); in other one embodiment, preserving the oldvalue of each element of the destination where the corresponding maskbit has a 0. In contrast, when zeroing vector masks allow any set ofelements in the destination to be zeroed during the execution of anyoperation (specified by the base operation and the augmentationoperation); in one embodiment, an element of the destination is set to 0when the corresponding mask bit has a 0 value. A subset of thisfunctionality is the ability to control the vector length of theoperation being performed (that is, the span of elements being modified,from the first to the last one); however, it is not necessary that theelements that are modified be consecutive. Thus, the write mask field2170 allows for partial vector operations, including loads, stores,arithmetic, logical, etc. While embodiments of the invention aredescribed in which the write mask field's 2170 content selects one of anumber of write mask registers that contains the write mask to be used(and thus the write mask field's 2170 content indirectly identifies thatmasking to be performed), alternative embodiments instead or additionalallow the mask write field's 2170 content to directly specify themasking to be performed.

Immediate field 2172—its content allows for the specification of animmediate. This field is optional in the sense that is it not present inan implementation of the generic vector friendly format that does notsupport immediate and it is not present in instructions that do not usean immediate.

Class field 2168—its content distinguishes between different classes ofinstructions. With reference to FIGS. 21A-B, the contents of this fieldselect between class A and class B instructions. In FIGS. 21A-B, roundedcorner squares are used to indicate a specific value is present in afield (e.g., class A 2168A and class B 2168B for the class field 2168respectively in FIGS. 21A-B).

Instruction Templates of Class A

In the case of the non-memory access 2105 instruction templates of classA, the alpha field 2152 is interpreted as an RS field 2152A, whosecontent distinguishes which one of the different augmentation operationtypes are to be performed (e.g., round 2152A.1 and data transform2152A.2 are respectively specified for the no memory access, round typeoperation 2110 and the no memory access, data transform type operation2115 instruction templates), while the beta field 2154 distinguisheswhich of the operations of the specified type is to be performed. In theno memory access 2105 instruction templates, the scale field 2160, thedisplacement field 2162A, and the displacement scale filed 2162B are notpresent.

No-Memory Access Instruction Templates—Full Round Control Type Operation

In the no memory access full round control type operation 2110instruction template, the beta field 2154 is interpreted as a roundcontrol field 2154A, whose content(s) provide static rounding. While inthe described embodiments of the invention the round control field 2154Aincludes a suppress all floating point exceptions (SAE) field 2156 and around operation control field 2158, alternative embodiments may supportmay encode both these concepts into the same field or only have one orthe other of these concepts/fields (e.g., may have only the roundoperation control field 2158).

SAE field 2156—its content distinguishes whether or not to disable theexception event reporting; when the SAE field's 2156 content indicatessuppression is enabled, a given instruction does not report any kind offloating-point exception flag and does not raise any floating pointexception handler.

Round operation control field 2158—its content distinguishes which oneof a group of rounding operations to perform (e.g., Round-up,Round-down, Round-towards-zero and Round-to-nearest). Thus, the roundoperation control field 2158 allows for the changing of the roundingmode on a per instruction basis. In one embodiment of the inventionwhere a processor includes a control register for specifying roundingmodes, the round operation control field's 2150 content overrides thatregister value.

No Memory Access Instruction Templates—Data Transform Type Operation

In the no memory access data transform type operation 2115 instructiontemplate, the beta field 2154 is interpreted as a data transform field2154B, whose content distinguishes which one of a number of datatransforms is to be performed (e.g., no data transform, swizzle,broadcast).

In the case of a memory access 2120 instruction template of class A, thealpha field 2152 is interpreted as an eviction hint field 2152B, whosecontent distinguishes which one of the eviction hints is to be used (inFIG. 21A, temporal 2152B.1 and non-temporal 2152B.2 are respectivelyspecified for the memory access, temporal 2125 instruction template andthe memory access, non-temporal 2130 instruction template), while thebeta field 2154 is interpreted as a data manipulation field 2154C, whosecontent distinguishes which one of a number of data manipulationoperations (also known as primitives) is to be performed (e.g., nomanipulation; broadcast; up conversion of a source; and down conversionof a destination). The memory access 2120 instruction templates includethe scale field 2160, and optionally the displacement field 2162A or thedisplacement scale field 2162B.

Vector memory instructions perform vector loads from and vector storesto memory, with conversion support. As with regular vector instructions,vector memory instructions transfer data from/to memory in a dataelement-wise fashion, with the elements that are actually transferred isdictated by the contents of the vector mask that is selected as thewrite mask.

Memory Access Instruction Templates—Temporal

Temporal data is data likely to be reused soon enough to benefit fromcaching. This is, however, a hint, and different processors mayimplement it in different ways, including ignoring the hint entirely.

Memory Access Instruction Templates—Non-Temporal

Non-temporal data is data unlikely to be reused soon enough to benefitfrom caching in the 1st-level cache and should be given priority foreviction. This is, however, a hint, and different processors mayimplement it in different ways, including ignoring the hint entirely.

Instruction Templates of Class B

In the case of the instruction templates of class B, the alpha field2152 is interpreted as a write mask control (Z) field 2152C, whosecontent distinguishes whether the write masking controlled by the writemask field 2170 should be a merging or a zeroing.

In the case of the non-memory access 2105 instruction templates of classB, part of the beta field 2154 is interpreted as an RL field 2157A,whose content distinguishes which one of the different augmentationoperation types are to be performed (e.g., round 2157A.1 and vectorlength (VSIZE) 2157A.2 are respectively specified for the no memoryaccess, write mask control, partial round control type operation 2112instruction template and the no memory access, write mask control, VSIZEtype operation 2117 instruction template), while the rest of the betafield 2154 distinguishes which of the operations of the specified typeis to be performed. In the no memory access 2105 instruction templates,the scale field 2160, the displacement field 2162A, and the displacementscale filed 2162B are not present.

In the no memory access, write mask control, partial round control typeoperation 2110 instruction template, the rest of the beta field 2154 isinterpreted as a round operation field 2159A and exception eventreporting is disabled (a given instruction does not report any kind offloating-point exception flag and does not raise any floating pointexception handler).

Round operation control field 2159A—just as round operation controlfield 2158, its content distinguishes which one of a group of roundingoperations to perform (e.g., Round-up, Round-down, Round-towards-zeroand Round-to-nearest). Thus, the round operation control field 2159Aallows for the changing of the rounding mode on a per instruction basis.In one embodiment of the invention where a processor includes a controlregister for specifying rounding modes, the round operation controlfield's 2150 content overrides that register value.

In the no memory access, write mask control, VSIZE type operation 2117instruction template, the rest of the beta field 2154 is interpreted asa vector length field 2159B, whose content distinguishes which one of anumber of data vector lengths is to be performed on (e.g., 128, 256, or512 byte).

In the case of a memory access 2120 instruction template of class B,part of the beta field 2154 is interpreted as a broadcast field 2157B,whose content distinguishes whether or not the broadcast type datamanipulation operation is to be performed, while the rest of the betafield 2154 is interpreted the vector length field 2159B. The memoryaccess 2120 instruction templates include the scale field 2160, andoptionally the displacement field 2162A or the displacement scale field2162B.

With regard to the generic vector friendly instruction format 2100, afull opcode field 2174 is shown including the format field 2140, thebase operation field 2142, and the data element width field 2164. Whileone embodiment is shown where the full opcode field 2174 includes all ofthese fields, the full opcode field 2174 includes less than all of thesefields in embodiments that do not support all of them. The full opcodefield 2174 provides the operation code (opcode).

The augmentation operation field 2150, the data element width field2164, and the write mask field 2170 allow these features to be specifiedon a per instruction basis in the generic vector friendly instructionformat.

The combination of write mask field and data element width field createtyped instructions in that they allow the mask to be applied based ondifferent data element widths.

The various instruction templates found within class A and class B arebeneficial in different situations. In some embodiments of theinvention, different processors or different cores within a processormay support only class A, only class B, or both classes. For instance, ahigh performance general purpose out-of-order core intended forgeneral-purpose computing may support only class B, a core intendedprimarily for graphics and/or scientific (throughput) computing maysupport only class A, and a core intended for both may support both (ofcourse, a core that has some mix of templates and instructions from bothclasses but not all templates and instructions from both classes iswithin the purview of the invention). Also, a single processor mayinclude multiple cores, all of which support the same class or in whichdifferent cores support different class. For instance, in a processorwith separate graphics and general purpose cores, one of the graphicscores intended primarily for graphics and/or scientific computing maysupport only class A, while one or more of the general purpose cores maybe high performance general purpose cores with out of order executionand register renaming intended for general-purpose computing thatsupport only class B. Another processor that does not have a separategraphics core, may include one more general purpose in-order orout-of-order cores that support both class A and class B. Of course,features from one class may also be implement in the other class indifferent embodiments of the invention. Programs written in a high levellanguage would be put (e.g., just in time compiled or staticallycompiled) into an variety of different executable forms, including: 1) aform having only instructions of the class(es) supported by the targetprocessor for execution; or 2) a form having alternative routineswritten using different combinations of the instructions of all classesand having control flow code that selects the routines to execute basedon the instructions supported by the processor which is currentlyexecuting the code.

Exemplary Specific Vector Friendly Instruction Format

FIG. 22 is a block diagram illustrating an exemplary specific vectorfriendly instruction format according to embodiments of the invention.FIG. 22 shows a specific vector friendly instruction format 2200 that isspecific in the sense that it specifies the location, size,interpretation, and order of the fields, as well as values for some ofthose fields. The specific vector friendly instruction format 2200 maybe used to extend the x86 instruction set, and thus some of the fieldsare similar or the same as those used in the existing x86 instructionset and extension thereof (e.g., AVX). This format remains consistentwith the prefix encoding field, real opcode byte field, MOD RIM field,SIB field, displacement field, and immediate fields of the existing x86instruction set with extensions. The fields from FIG. 21 into which thefields from FIG. 22 map are illustrated.

It should be understood that, although embodiments of the invention aredescribed with reference to the specific vector friendly instructionformat 2200 in the context of the generic vector friendly instructionformat 2100 for illustrative purposes, the invention is not limited tothe specific vector friendly instruction format 2200 except whereclaimed. For example, the generic vector friendly instruction format2100 contemplates a variety of possible sizes for the various fields,while the specific vector friendly instruction format 2200 is shown ashaving fields of specific sizes. By way of specific example, while thedata element width field 2164 is illustrated as a one bit field in thespecific vector friendly instruction format 2200, the invention is notso limited (that is, the generic vector friendly instruction format 2100contemplates other sizes of the data element width field 2164).

The generic vector friendly instruction format 2100 includes thefollowing fields listed below in the order illustrated in FIG. 22A.

EVEX Prefix (Bytes 0-3) 2202-is encoded in a four-byte form.

Format Field 2140 (EVEX Byte 0, bits [7:0])—the first byte (EVEX Byte 0)is the format field 2140 and it contains 0x62 (the unique value used fordistinguishing the vector friendly instruction format in one embodimentof the invention).

The second-fourth bytes (EVEX Bytes 1-3) include a number of bit fieldsproviding specific capability.

REX field 2205 (EVEX Byte 1, bits [7-5])—consists of a EVEX.R bit field(EVEX Byte 1, bit [7]—R), EVEX.X bit field (EVEX byte 1, bit [6]—X), and2157BEX byte 1, bit[5]—B). The EVEX.R, EVEX.X, and EVEX.B bit fieldsprovide the same functionality as the corresponding VEX bit fields, andare encoded using is complement form, i.e. ZMM0 is encoded as 1111B,ZMM15 is encoded as 0000B. Other fields of the instructions encode thelower three bits of the register indexes as is known in the art (rrr,xxx, and bbb), so that Rrrr, Xxxx, and Bbbb may be formed by addingEVEX.R, EVEX.X, and EVEX.B.

REX′ field 2110—this is the first part of the REX′ field 2110 and is theEVEX.R′ bit field (EVEX Byte 1, bit [4]—R′) that is used to encodeeither the upper 16 or lower 16 of the extended 32 register set. In oneembodiment of the invention, this bit, along with others as indicatedbelow, is stored in bit inverted format to distinguish (in thewell-known x86 32-bit mode) from the BOUND instruction, whose realopcode byte is 62, but does not accept in the MOD R/M field (describedbelow) the value of 11 in the MOD field; alternative embodiments of theinvention do not store this and the other indicated bits below in theinverted format. A value of 11s used to encode the lower 16 registers.In other words, R′Rrrr is formed by combining EVEX.R′, EVEX.R, and theother RRR from other fields.

Opcode map field 2215 (EVEX byte 1, bits [3:0]—mmmm)—its content encodesan implied leading opcode byte (0F, 0F 38, or 0F 3).

Data element width field 2164 (EVEX byte 2, bit [7]—W)— is representedby the notation EVEX.W. EVEX.W is used to define the granularity (size)of the datatype (either 32-bit data elements or 64-bit data elements).

EVEX.vvvv 2220 (EVEX Byte 2, bits [6:3]—vvvv)—the role of EVEX.vvvv mayinclude the following: 1) EVEX.vvvv encodes the first source registeroperand, specified in inverted (1s complement) form and is valid forinstructions with 2 or more source operands; 2) EVEX.vvvv encodes thedestination register operand, specified in 1s complement form forcertain vector shifts; or 3) EVEX.vvvv does not encode any operand, thefield is reserved and should contain 1111b. Thus, EVEX.vvvv field 2220encodes the 4 low-order bits of the first source register specifierstored in inverted (1s complement) form. Depending on the instruction,an extra different EVEX bit field is used to extend the specifier sizeto 32 registers.

EVEX.U 2168 Class field (EVEX byte 2, bit [2]—U)—If EVEX.U=0, itindicates class A or EVEX.U0; if EVEX.U=1, it indicates class B orEVEX.U1. Prefix encoding field 2225 (EVEX byte 2, bits[1:0]—pp)—provides additional bits for the base operation field. Inaddition to providing support for the legacy SSE instructions in theEVEX prefix format, this also has the benefit of compacting the SIMDprefix (rather than requiring a byte to express the SIMD prefix, theEVEX prefix requires only 2 bits). In one embodiment, to support legacySSE instructions that use a SIMD prefix (66H, F2H, F3H) in both thelegacy format and in the EVEX prefix format, these legacy SIMD prefixesare encoded into the SIMD prefix encoding field; and at runtime areexpanded into the legacy SIMD prefix prior to being provided to thedecoder's PLA (so the PLA can execute both the legacy and EVEX format ofthese legacy instructions without modification). Although newerinstructions could use the EVEX prefix encoding field's content directlyas an opcode extension, certain embodiments expand in a similar fashionfor consistency but allow for different meanings to be specified bythese legacy SIMD prefixes. An alternative embodiment may redesign thePLA to support the 2 bit SIMD prefix encodings, and thus not require theexpansion.

Alpha field 2152 (EVEX byte 3, bit [7]—EH; also known as EVEX.EH,EVEX.rs, EVEX.RL, EVEX.write mask control, and EVEX.N; also illustratedwith α)—as previously described, this field is context specific.

Beta field 2154 (EVEX byte 3, bits [6:4]—SSS, also known as EVEX.s₂₋₀,EVEX.r₂₋₀, EVEX.rr1, EVEX.LL0, EVEX.LLB; also illustrated with βββ)—aspreviously described, this field is context specific.

REX′ field 2110—this is the remainder of the REX′ field and is theEVEX.V′ bit field (EVEX Byte 3, bit [3]—V′) that may be used to encodeeither the upper 16 or lower 16 of the extended 32 register set. Thisbit is stored in bit inverted format. A value of 1 is used to encode thelower 16 registers. In other words, V′VVVV is formed by combiningEVEX.V′, EVEX.vvvv.

Write mask field 2170 (EVEX byte 3, bits [2:0]—kkk)—its contentspecifies the index of a register in the write mask registers aspreviously described. In one embodiment of the invention, the specificvalue EVEX kkk=000 has a special behavior implying no write mask is usedfor the particular instruction (this may be implemented in a variety ofways including the use of a write mask hardwired to all ones or hardwarethat bypasses the masking hardware).

Real Opcode Field 2230 (Byte 4) is also known as the opcode byte. Partof the opcode is specified in this field.

MOD R/M Field 2240 (Byte 5) includes MOD field 2242, Reg field 2244, andR/M field 2246. As previously described, the MOD field's 2242 contentdistinguishes between memory access and non-memory access operations.The role of Reg field 2244 can be summarized to two situations: encodingeither the destination register operand or a source register operand, orbe treated as an opcode extension and not used to encode any instructionoperand. The role of R/M field 2246 may include the following: encodingthe instruction operand that references a memory address, or encodingeither the destination register operand or a source register operand.

Scale, Index, Base (SIB) Byte (Byte 6)—As previously described, thescale field's 2150 content is used for memory address generation.SIB.xxx 2254 and SIB.bbb 2256—the contents of these fields have beenpreviously referred to with regard to the register indexes Xxxx andBbbb.

Displacement field 2162A (Bytes 7-10)—when MOD field 2242 contains 10,bytes 7-10 are the displacement field 2162A, and it works the same asthe legacy 32-bit displacement (disp32) and works at byte granularity.

Displacement factor field 2162B (Byte 7)—when MOD field 2242 contains01, byte 7 is the displacement factor field 2162B. The location of thisfield is that same as that of the legacy x86 instruction set 8-bitdisplacement (disp8), which works at byte granularity. Since disp8 issign extended, it can only address between −128 and 127 bytes offsets;in terms of 64 byte cache lines, disp8 uses 8 bits that can be set toonly four really useful values −128, −64, 0, and 64; since a greaterrange is often needed, disp32 is used; however, disp32 requires 4 bytes.In contrast to disp8 and disp32, the displacement factor field 2162B isa reinterpretation of disp8; when using displacement factor field 2162B,the actual displacement is determined by the content of the displacementfactor field multiplied by the size of the memory operand access (N).This type of displacement is referred to as disp8*N. This reduces theaverage instruction length (a single byte of used for the displacementbut with a much greater range). Such compressed displacement is based onthe assumption that the effective displacement is multiple of thegranularity of the memory access, and hence, the redundant low-orderbits of the address offset do not need to be encoded. In other words,the displacement factor field 2162B substitutes the legacy x86instruction set 8-bit displacement. Thus, the displacement factor field2162B is encoded the same way as an x86 instruction set 8-bitdisplacement (so no changes in the ModRM/SIB encoding rules) with theonly exception that disp8 is overloaded to disp8*N. In other words,there are no changes in the encoding rules or encoding lengths but onlyin the interpretation of the displacement value by hardware (which needsto scale the displacement by the size of the memory operand to obtain abyte-wise address offset).

Immediate field 2172 operates as previously described.

Full Opcode Field

FIG. 22B is a block diagram illustrating the fields of the specificvector friendly instruction format 2200 that make up the full opcodefield 2174 according to one embodiment of the invention. Specifically,the full opcode field 2174 includes the format field 2140, the baseoperation field 2142, and the data element width (W) field 2164. Thebase operation field 2142 includes the prefix encoding field 2225, theopcode map field 2215, and the real opcode field 2230.

Register Index Field

FIG. 22C is a block diagram illustrating the fields of the specificvector friendly instruction format 2200 that make up the register indexfield 2144 according to one embodiment of the invention. Specifically,the register index field 2144 includes the REX field 2205, the REX′field 2210, the MODR/M.reg field 2244, the MODR/M.r/m field 2246, theVVVV field 2220, xxx field 2254, and the bbb field 2256.

Augmentation Operation Field

FIG. 22D is a block diagram illustrating the fields of the specificvector friendly instruction format 2200 that make up the augmentationoperation field 2150 according to one embodiment of the invention. Whenthe class (U) field 2168 contains 0, it signifies EVEX.U0 (class A2168A); when it contains 1, it signifies EVEX.U1 (class B 2168B). WhenU=0 and the MOD field 2242 contains 11 (signifying a no memory accessoperation), the alpha field 2152 (EVEX byte 3, bit [7]—EH) isinterpreted as the rs field 2152A. When the rs field 2152A contains a 1(round 2152A.1), the beta field 2154 (EVEX byte 3, bits [6:4]—SSS) isinterpreted as the round control field 2154A. The round control field2154A includes a one bit SAE field 2156 and a two bit round operationfield 2158. When the rs field 2152A contains a 0 (data transform2152A.2), the beta field 2154 (EVEX byte 3, bits [6:4]—SSS) isinterpreted as a three bit data transform field 2154B. When U=0 and theMOD field 2242 contains 00, 01, or 10 (signifying a memory accessoperation), the alpha field 2152 (EVEX byte 3, bit [7]—EH) isinterpreted as the eviction hint (EH) field 2152B and the beta field2154 (EVEX byte 3, bits [6:4]—SSS) is interpreted as a three bit datamanipulation field 2154C.

When U=1, the alpha field 2152 (EVEX byte 3, bit [7]—EH) is interpretedas the write mask control (Z) field 2152C. When U=1 and the MOD field2242 contains 11 (signifying a no memory access operation), part of thebeta field 2154 (EVEX byte 3, bit [4]—S₀) is interpreted as the RL field2157A; when it contains a 1 (round 2157A.1) the rest of the beta field2154 (EVEX byte 3, bit [6-5]—S₂₋₁) is interpreted as the round operationfield 2159A, while when the RL field 2157A contains a 0 (VSIZE 2157.A2)the rest of the beta field 2154 (EVEX byte 3, bit [6-5]—S₂₋₁) isinterpreted as the vector length field 2159B (EVEX byte 3, bit[6-5]—L₁₋₀). When U=1 and the MOD field 2242 contains 00, 01, or 10(signifying a memory access operation), the beta field 2154 (EVEX byte3, bits [6:4]—SSS) is interpreted as the vector length field 2159B (EVEXbyte 3, bit [6-5]—L₁₀) and the broadcast field 2157B (EVEX byte 3, bit[4]—B).

Exemplary Register Architecture

FIG. 23 is a block diagram of a register architecture 2300 according toone embodiment of the invention. In the embodiment illustrated, thereare 32 vector registers 2310 that are 512 bits wide; these registers arereferenced as zmm0 through zmm31. The lower order 256 bits of the lower16 zmm registers are overlaid on registers ymm0-16. The lower order 128bits of the lower 16 zmm registers (the lower order 128 bits of the ymmregisters) are overlaid on registers xmm0-15. The specific vectorfriendly instruction format 2200 operates on these overlaid registerfile as illustrated in the below tables.

Adjustable Vector Length Class Operations Registers Instruction A 2110,2115, zmm registers (the Templates that (FIG. 21A; 2125, 2130 vectorlength is 64 do not include U = 0) byte) the vector B 2112 zmm registers(the length field (FIG. 21B; vector length is 64 2159B U = 1) byte)Instruction B 2117, 2127 zmm, ymm, or xmm templates that (FIG. 21B;registers (the vector do include the U = 1) length is 64 byte, vectorlength 32 byte, or 16 byte) field 2159B depending on the vector lengthfield 2159BIn other words, the vector length field 2159B selects between a maximumlength and one or more other shorter lengths, where each such shorterlength is half the length of the preceding length; and instructionstemplates without the vector length field 2159B operate on the maximumvector length. Further, in one embodiment, the class B instructiontemplates of the specific vector friendly instruction format 2200operate on packed or scalar single/double-precision floating point dataand packed or scalar integer data. Scalar operations are operationsperformed on the lowest order data element position in an zmm/ymm/xmmregister; the higher order data element positions are either left thesame as they were prior to the instruction or zeroed depending on theembodiment.

Write mask registers 2315—in the embodiment illustrated, there are 8write mask registers (k0 through k7), each 64 bits in size. In analternate embodiment, the write mask registers 2315 are 16 bits in size.As previously described, in one embodiment of the invention, the vectormask register k0 cannot be used as a write mask; when the encoding thatwould normally indicate k0 is used for a write mask, it selects ahardwired write mask of 0xFFFF, effectively disabling write masking forthat instruction.

General-purpose registers 2325—in the embodiment illustrated, there aresixteen 64-bit general-purpose registers that are used along with theexisting x86 addressing modes to address memory operands. Theseregisters are referenced by the names RAX, RBX, RCX, RDX, RBP, RSI, RDI,RSP, and R8 through R15.

Scalar floating point stack register file (x87 stack) 2345, on which isaliased the MMX packed integer flat register file 2350—in the embodimentillustrated, the x87 stack is an eight-element stack used to performscalar floating-point operations on 32/64/80-bit floating point datausing the x87 instruction set extension; while the MMX registers areused to perform operations on 64-bit packed integer data, as well as tohold operands for some operations performed between the MMX and XMMregisters.

Alternative embodiments of the invention may use wider or narrowerregisters. Additionally, alternative embodiments of the invention mayuse more, less, or different register files and registers.

Exemplary Core Architectures, Processors, and Computer Architectures

Processor cores may be implemented in different ways, for differentpurposes, and in different processors. For instance, implementations ofsuch cores may include: 1) a general purpose in-order core intended forgeneral-purpose computing; 2) a high performance general purposeout-of-order core intended for general-purpose computing; 3) a specialpurpose core intended primarily for graphics and/or scientific(throughput) computing. Implementations of different processors mayinclude: 1) a CPU including one or more general purpose in-order coresintended for general-purpose computing and/or one or more generalpurpose out-of-order cores intended for general-purpose computing; and2) a coprocessor including one or more special purpose cores intendedprimarily for graphics and/or scientific (throughput). Such differentprocessors lead to different computer system architectures, which mayinclude: 1) the coprocessor on a separate chip from the CPU; 2) thecoprocessor on a separate die in the same package as a CPU; 3) thecoprocessor on the same die as a CPU (in which case, such a coprocessoris sometimes referred to as special purpose logic, such as integratedgraphics and/or scientific (throughput) logic, or as special purposecores); and 4) a system on a chip that may include on the same die thedescribed CPU (sometimes referred to as the application core(s) orapplication processor(s)), the above described coprocessor, andadditional functionality. Exemplary core architectures are describednext, followed by descriptions of exemplary processors and computerarchitectures.

Exemplary Core Architectures In-Order and Out-of-Order Core BlockDiagram

FIG. 24A is a block diagram illustrating both an exemplary in-orderpipeline and an exemplary register renaming, out-of-orderissue/execution pipeline according to embodiments of the invention. FIG.24B is a block diagram illustrating both an exemplary embodiment of anin-order architecture core and an exemplary register renaming,out-of-order issue/execution architecture core to be included in aprocessor according to embodiments of the invention. The solid linedboxes in FIGS. 24A-B illustrate the in-order pipeline and in-order core,while the optional addition of the dashed lined boxes illustrates theregister renaming, out-of-order issue/execution pipeline and core. Giventhat the in-order aspect is a subset of the out-of-order aspect, theout-of-order aspect will be described.

In FIG. 24A, a processor pipeline 2400 includes a fetch stage 2402, alength decode stage 2404, a decode stage 2406, an allocation stage 2408,a renaming stage 2410, a scheduling (also known as a dispatch or issue)stage 2412, a register read/memory read stage 2414, an execute stage2416, a write back/memory write stage 2418, an exception handling stage2422, and a commit stage 2424.

FIG. 24B shows processor core 2490 including a front end unit 2430coupled to an execution engine unit 2450, and both are coupled to amemory unit 2470. The core 2490 may be a reduced instruction setcomputing (RISC) core, a complex instruction set computing (CISC) core,a very long instruction word (VLIW) core, or a hybrid or alternativecore type. As yet another option, the core 2490 may be a special-purposecore, such as, for example, a network or communication core, compressionengine, coprocessor core, general purpose computing graphics processingunit (GPGPU) core, graphics core, or the like.

The front end unit 2430 includes a branch prediction unit 2432 coupledto an instruction cache unit 2434, which is coupled to an instructiontranslation lookaside buffer (TLB) 2436, which is coupled to aninstruction fetch unit 2438, which is coupled to a decode unit 2440. Thedecode unit 2440 (or decoder) may decode instructions, and generate asan output one or more micro-operations, micro-code entry points,microinstructions, other instructions, or other control signals, whichare decoded from, or which otherwise reflect, or are derived from, theoriginal instructions. The decode unit 2440 may be implemented usingvarious different mechanisms. Examples of suitable mechanisms include,but are not limited to, look-up tables, hardware implementations,programmable logic arrays (PLAs), microcode read only memories (ROMs),etc. In one embodiment, the core 2490 includes a microcode ROM or othermedium that stores microcode for certain macroinstructions (e.g., indecode unit 2440 or otherwise within the front end unit 2430). Thedecode unit 2440 is coupled to a rename/allocator unit 2452 in theexecution engine unit 2450.

The execution engine unit 2450 includes the rename/allocator unit 2452coupled to a retirement unit 2454 and a set of one or more schedulerunit(s) 2456. The scheduler unit(s) 2456 represents any number ofdifferent schedulers, including reservations stations, centralinstruction window, etc. The scheduler unit(s) 2456 is coupled to thephysical register file(s) unit(s) 2458. Each of the physical registerfile(s) units 2458 represents one or more physical register files,different ones of which store one or more different data types, such asscalar integer, scalar floating point, packed integer, packed floatingpoint, vector integer, vector floating point, status (e.g., aninstruction pointer that is the address of the next instruction to beexecuted), etc. In one embodiment, the physical register file(s) unit2458 comprises a vector registers unit, a write mask registers unit, anda scalar registers unit. These register units may provide architecturalvector registers, vector mask registers, and general purpose registers.The physical register file(s) unit(s) 2458 is overlapped by theretirement unit 2454 to illustrate various ways in which registerrenaming and out-of-order execution may be implemented (e.g., using areorder buffer(s) and a retirement register file(s); using a futurefile(s), a history buffer(s), and a retirement register file(s); using aregister maps and a pool of registers; etc.). The retirement unit 2454and the physical register file(s) unit(s) 2458 are coupled to theexecution cluster(s) 2460. The execution cluster(s) 2460 includes a setof one or more execution units 2462 and a set of one or more memoryaccess units 2464. The execution units 2462 may perform variousoperations (e.g., shifts, addition, subtraction, multiplication) and onvarious types of data (e.g., scalar floating point, packed integer,packed floating point, vector integer, vector floating point). Whilesome embodiments may include a number of execution units dedicated tospecific functions or sets of functions, other embodiments may includeonly one execution unit or multiple execution units that all perform allfunctions. The scheduler unit(s) 2456, physical register file(s) unit(s)2458, and execution cluster(s) 2460 are shown as being possibly pluralbecause certain embodiments create separate pipelines for certain typesof data/operations (e.g., a scalar integer pipeline, a scalar floatingpoint/packed integer/packed floating point/vector integer/vectorfloating point pipeline, and/or a memory access pipeline that each havetheir own scheduler unit, physical register file(s) unit, and/orexecution cluster—and in the case of a separate memory access pipeline,certain embodiments are implemented in which only the execution clusterof this pipeline has the memory access unit(s) 2464). It should also beunderstood that where separate pipelines are used, one or more of thesepipelines may be out-of-order issue/execution and the rest in-order.

The set of memory access units 2464 is coupled to the memory unit 2470,which includes a data TLB unit 2472 coupled to a data cache unit 2474coupled to a level 2 (L2) cache unit 2476. In one exemplary embodiment,the memory access units 2464 may include a load unit, a store addressunit, and a store data unit, each of which is coupled to the data TLBunit 2472 in the memory unit 2470. The instruction cache unit 2434 isfurther coupled to a level 2 (L2) cache unit 2476 in the memory unit2470. The L2 cache unit 2476 is coupled to one or more other levels ofcache and eventually to a main memory.

By way of example, the exemplary register renaming, out-of-orderissue/execution core architecture may implement the pipeline 2400 asfollows: 1) the instruction fetch 2438 performs the fetch and lengthdecoding stages 2402 and 2404; 2) the decode unit 2440 performs thedecode stage 2406; 3) the rename/allocator unit 2452 performs theallocation stage 2408 and renaming stage 2410; 4) the scheduler unit(s)2456 performs the schedule stage 2412; 5) the physical register file(s)unit(s) 2458 and the memory unit 2470 perform the register read/memoryread stage 2414; the execution cluster 2460 perform the execute stage2416; 6) the memory unit 2470 and the physical register file(s) unit(s)2458 perform the write back/memory write stage 2418; 7) various unitsmay be involved in the exception handling stage 2422; and 8) theretirement unit 2454 and the physical register file(s) unit(s) 2458perform the commit stage 2424.

The core 2490 may support one or more instructions sets (e.g., the x86instruction set (with some extensions that have been added with newerversions); the MIPS instruction set of MIPS Technologies of Sunnyvale,Calif.; the ARM instruction set (with optional additional extensionssuch as NEON) of ARM Holdings of Sunnyvale, Calif.), including theinstruction(s) described herein. In one embodiment, the core 2490includes logic to support a packed data instruction set extension (e.g.,AVX1, AVX2), thereby allowing the operations used by many multimediaapplications to be performed using packed data.

It should be understood that the core may support multithreading(executing two or more parallel sets of operations or threads), and maydo so in a variety of ways including time sliced multithreading,simultaneous multithreading (where a single physical core provides alogical core for each of the threads that physical core issimultaneously multithreading), or a combination thereof (e.g., timesliced fetching and decoding and simultaneous multithreading thereaftersuch as in the Intel® Hyperthreading technology).

While register renaming is described in the context of out-of-orderexecution, it should be understood that register renaming may be used inan in-order architecture. While the illustrated embodiment of theprocessor also includes separate instruction and data cache units2434/2474 and a shared L2 cache unit 2476, alternative embodiments mayhave a single internal cache for both instructions and data, such as,for example, a Level 1 (L1) internal cache, or multiple levels ofinternal cache. In some embodiments, the system may include acombination of an internal cache and an external cache that is externalto the core and/or the processor. Alternatively, all of the cache may beexternal to the core and/or the processor.

Specific Exemplary In-Order Core Architecture

FIGS. 25A-B illustrate a block diagram of a more specific exemplaryin-order core architecture, which core would be one of several logicblocks (including other cores of the same type and/or different types)in a chip. The logic blocks communicate through a high-bandwidthinterconnect network (e.g., a ring network) with some fixed functionlogic, memory I/O interfaces, and other necessary I/O logic, dependingon the application.

FIG. 25A is a block diagram of a single processor core, along with itsconnection to the on-die interconnect network 2502 and with its localsubset of the Level 2 (L2) cache 2504, according to embodiments of theinvention. In one embodiment, an instruction decoder 2500 supports thex86 instruction set with a packed data instruction set extension. An L1cache 2506 allows low-latency accesses to cache memory into the scalarand vector units. While in one embodiment (to simplify the design), ascalar unit 2508 and a vector unit 2510 use separate register sets(respectively, scalar registers 2512 and vector registers 2514) and datatransferred between them is written to memory and then read back in froma level 1 (L1) cache 2506, alternative embodiments of the invention mayuse a different approach (e.g., use a single register set or include acommunication path that allow data to be transferred between the tworegister files without being written and read back).

The local subset of the L2 cache 2504 is part of a global L2 cache thatis divided into separate local subsets, one per processor core. Eachprocessor core has a direct access path to its own local subset of theL2 cache 2504. Data read by a processor core is stored in its L2 cachesubset 2504 and can be accessed quickly, in parallel with otherprocessor cores accessing their own local L2 cache subsets. Data writtenby a processor core is stored in its own L2 cache subset 2504 and isflushed from other subsets, if necessary. The ring network ensurescoherency for shared data. The ring network is bi-directional to allowagents such as processor cores, L2 caches and other logic blocks tocommunicate with each other within the chip. Each ring data-path is1012-bits wide per direction.

FIG. 25B is an expanded view of part of the processor core in FIG. 25Aaccording to embodiments of the invention. FIG. 25B includes an L1 datacache 2506A part of the L1 cache 2504, as well as more detail regardingthe vector unit 2510 and the vector registers 2514. Specifically, thevector unit 2510 is a 16-wide vector processing unit (VPU) (see the16-wide ALU 2528), which executes one or more of integer,single-precision float, and double-precision float instructions. The VPUsupports swizzling the register inputs with swizzle unit 2520, numericconversion with numeric convert units 2522A-B, and replication withreplication unit 2524 on the memory input. Write mask registers 2526allow predicating resulting vector writes.

Processor with Integrated Memory Controller and Graphics

FIG. 26 is a block diagram of a processor 2600 that may have more thanone core, may have an integrated memory controller, and may haveintegrated graphics according to embodiments of the invention. The solidlined boxes in FIG. 26 illustrate a processor 2600 with a single core2602A, a system agent 2610, a set of one or more bus controller units2616, while the optional addition of the dashed lined boxes illustratesan alternative processor 2600 with multiple cores 2602A-N, a set of oneor more integrated memory controller unit(s) 2614 in the system agentunit 2610, and special purpose logic 2608.

Thus, different implementations of the processor 2600 may include: 1) aCPU with the special purpose logic 2608 being integrated graphics and/orscientific (throughput) logic (which may include one or more cores), andthe cores 2602A-N being one or more general purpose cores (e.g., generalpurpose in-order cores, general purpose out-of-order cores, acombination of the two); 2) a coprocessor with the cores 2602A-N being alarge number of special purpose cores intended primarily for graphicsand/or scientific (throughput); and 3) a coprocessor with the cores2602A-N being a large number of general purpose in-order cores. Thus,the processor 2600 may be a general-purpose processor, coprocessor orspecial-purpose processor, such as, for example, a network orcommunication processor, compression engine, graphics processor, GPGPU(general purpose graphics processing unit), a high-throughput manyintegrated core (MIC) coprocessor (including 30 or more cores), embeddedprocessor, or the like. The processor may be implemented on one or morechips. The processor 2600 may be a part of and/or may be implemented onone or more substrates using any of a number of process technologies,such as, for example, BiCMOS, CMOS, or NMOS.

The memory hierarchy includes one or more levels of cache within thecores, a set or one or more shared cache units 2606, and external memory(not shown) coupled to the set of integrated memory controller units2614. The set of shared cache units 2606 may include one or moremid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), orother levels of cache, a last level cache (LLC), and/or combinationsthereof. While in one embodiment a ring based interconnect unit 2612interconnects the integrated graphics logic 2608, the set of sharedcache units 2606, and the system agent unit 2610/integrated memorycontroller unit(s) 2614, alternative embodiments may use any number ofwell-known techniques for interconnecting such units. In one embodiment,coherency is maintained between one or more cache units 2606 and cores2602-A-N.

In some embodiments, one or more of the cores 2602A-N are capable ofmulti-threading. The system agent 2610 includes those componentscoordinating and operating cores 2602A-N. The system agent unit 2610 mayinclude for example a power control unit (PCU) and a display unit. ThePCU may be or include logic and components needed for regulating thepower state of the cores 2602A-N and the integrated graphics logic 2608.The display unit is for driving one or more externally connecteddisplays.

The cores 2602A-N may be homogenous or heterogeneous in terms ofarchitecture instruction set; that is, two or more of the cores 2602A-Nmay be capable of execution the same instruction set, while others maybe capable of executing only a subset of that instruction set or adifferent instruction set.

Exemplary Computer Architectures

FIGS. 27-30 are block diagrams of exemplary computer architectures.Other system designs and configurations known in the arts for laptops,desktops, handheld PCs, personal digital assistants, engineeringworkstations, servers, network devices, network hubs, switches, embeddedprocessors, digital signal processors (DSPs), graphics devices, videogame devices, set-top boxes, micro controllers, cell phones, portablemedia players, hand held devices, and various other electronic devices,are also suitable. In general, a huge variety of systems or electronicdevices capable of incorporating a processor and/or other executionlogic as disclosed herein are generally suitable.

Referring now to FIG. 27, shown is a block diagram of a system 2700 inaccordance with one embodiment of the present invention. The system 2700may include one or more processors 2710, 2715, which are coupled to acontroller hub 2720. In one embodiment the controller hub 2720 includesa graphics memory controller hub (GMCH) 2790 and an Input/Output Hub(IOH) 2750 (which may be on separate chips); the GMCH 2790 includesmemory and graphics controllers to which are coupled memory 2740 and acoprocessor 2745; the IOH 2750 is couples input/output (I/O) devices2760 to the GMCH 2790. Alternatively, one or both of the memory andgraphics controllers are integrated within the processor (as describedherein), the memory 2740 and the coprocessor 2745 are coupled directlyto the processor 2710, and the controller hub 2720 in a single chip withthe IOH 2750.

The optional nature of additional processors 2715 is denoted in FIG. 27with broken lines. Each processor 2710, 2715 may include one or more ofthe processing cores described herein and may be some version of theprocessor 2600.

The memory 2740 may be, for example, dynamic random access memory(DRAM), phase change memory (PCM), or a combination of the two. For atleast one embodiment, the controller hub 2720 communicates with theprocessor(s) 2710, 2715 via a multi-drop bus, such as a frontside bus(FSB), point-to-point interface such as QuickPath Interconnect (QPI), orsimilar connection 2795.

In one embodiment, the coprocessor 2745 is a special-purpose processor,such as, for example, a high-throughput MIC processor, a network orcommunication processor, compression engine, graphics processor, GPGPU,embedded processor, or the like. In one embodiment, controller hub 2720may include an integrated graphics accelerator.

There can be a variety of differences between the physical resources2710, 2715 in terms of a spectrum of metrics of merit includingarchitectural, microarchitectural, thermal, power consumptioncharacteristics, and the like.

In one embodiment, the processor 2710 executes instructions that controldata processing operations of a general type. Embedded within theinstructions may be coprocessor instructions. The processor 2710recognizes these coprocessor instructions as being of a type that shouldbe executed by the attached coprocessor 2745. Accordingly, the processor2710 issues these coprocessor instructions (or control signalsrepresenting coprocessor instructions) on a coprocessor bus or otherinterconnect, to coprocessor 2745. Coprocessor(s) 2745 accept andexecute the received coprocessor instructions.

Referring now to FIG. 28, shown is a block diagram of a first morespecific exemplary system 2800 in accordance with an embodiment of thepresent invention. As shown in FIG. 28, multiprocessor system 2800 is apoint-to-point interconnect system, and includes a first processor 2870and a second processor 2880 coupled via a point-to-point interconnect2850. Each of processors 2870 and 2880 may be some version of theprocessor 2600. In one embodiment of the invention, processors 2870 and2880 are respectively processors 2710 and 2715, while coprocessor 2838is coprocessor 2745. In another embodiment, processors 2870 and 2880 arerespectively processor 2710 coprocessor 2745.

Processors 2870 and 2880 are shown including integrated memorycontroller (IMC) units 2872 and 2882, respectively. Processor 2870 alsoincludes as part of its bus controller units point-to-point (P-P)interfaces 2876 and 2878; similarly, second processor 2880 includes P-Pinterfaces 2886 and 2888. Processors 2870, 2880 may exchange informationvia a point-to-point (P-P) interface 2850 using P-P interface circuits2878, 2888. As shown in FIG. 28, IMCs 2872 and 2882 couple theprocessors to respective memories, namely a memory 2832 and a memory2834, which may be portions of main memory locally attached to therespective processors.

Processors 2870, 2880 may each exchange information with a chipset 2890via individual P-P interfaces 2852, 2854 using point to point interfacecircuits 2876, 2894, 2886, 2898. Chipset 2890 may optionally exchangeinformation with the coprocessor 2838 via a high-performance interface2839. In one embodiment, the coprocessor 2838 is a special-purposeprocessor, such as, for example, a high-throughput MIC processor, anetwork or communication processor, compression engine, graphicsprocessor, GPGPU, embedded processor, or the like.

A shared cache (not shown) may be included in either processor oroutside of both processors, yet connected with the processors via P-Pinterconnect, such that either or both processors' local cacheinformation may be stored in the shared cache if a processor is placedinto a low power mode.

Chipset 2890 may be coupled to a first bus 2816 via an interface 2896.In one embodiment, first bus 2816 may be a Peripheral ComponentInterconnect (PCI) bus, or a bus such as a PCI Express bus or anotherthird generation I/O interconnect bus, although the scope of the presentinvention is not so limited.

As shown in FIG. 28, various I/O devices 2814 may be coupled to firstbus 2816, along with a bus bridge 2818 which couples first bus 2816 to asecond bus 2820. In one embodiment, one or more additional processor(s)2815, such as coprocessors, high-throughput MIC processors, GPGPU's,accelerators (such as, e.g., graphics accelerators or digital signalprocessing (DSP) units), field programmable gate arrays, or any otherprocessor, are coupled to first bus 2816. In one embodiment, second bus2820 may be a low pin count (LPC) bus. Various devices may be coupled toa second bus 2820 including, for example, a keyboard and/or mouse 2822,communication devices 2827 and a storage unit 2828 such as a disk driveor other mass storage device which may include instructions/code anddata 2830, in one embodiment. Further, an audio I/O 2824 may be coupledto the second bus 2820. Note that other architectures are possible. Forexample, instead of the point-to-point architecture of FIG. 28, a systemmay implement a multi-drop bus or other such architecture.

Referring now to FIG. 29, shown is a block diagram of a second morespecific exemplary system 2900 in accordance with an embodiment of thepresent invention. Like elements in FIGS. 28 and 29 bear like referencenumerals, and certain aspects of FIG. 28 have been omitted from FIG. 29in order to avoid obscuring other aspects of FIG. 29.

FIG. 29 illustrates that the processors 2870, 2880 may includeintegrated memory and I/O control logic (“CL”) 2872 and 2882,respectively. Thus, the CL 2872, 2882 include integrated memorycontroller units and include I/O control logic.

FIG. 29 illustrates that not only are the memories 2832, 2834 coupled tothe CL 2872, 2882, but also that I/O devices 2914 are also coupled tothe control logic 2872, 2882. Legacy I/O devices 2915 are coupled to thechipset 2890.

Referring now to FIG. 30, shown is a block diagram of a SoC 3000 inaccordance with an embodiment of the present invention. Similar elementsin FIG. 26 bear like reference numerals. Also, dashed lined boxes areoptional features on more advanced SoCs. In FIG. 30, an interconnectunit(s) 3002 is coupled to: an application processor 3010 which includesa set of one or more cores 202A-N and shared cache unit(s) 2606; asystem agent unit 2610; a bus controller unit(s) 2616; an integratedmemory controller unit(s) 2614; a set or one or more coprocessors 3020which may include integrated graphics logic, an image processor, anaudio processor, and a video processor; an static random access memory(SRAM) unit 3030; a direct memory access (DMA) unit 3032; and a displayunit 3040 for coupling to one or more external displays. In oneembodiment, the coprocessor(s) 3020 include a special-purpose processor,such as, for example, a network or communication processor, compressionengine, GPGPU, a high-throughput MIC processor, embedded processor, orthe like.

Embodiments of the mechanisms disclosed herein may be implemented inhardware, software, firmware, or a combination of such implementationapproaches. Embodiments of the invention may be implemented as computerprograms or program code executing on programmable systems comprising atleast one processor, a storage system (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device.

Program code, such as code 2830 illustrated in FIG. 28, may be appliedto input instructions to perform the functions described herein andgenerate output information. The output information may be applied toone or more output devices, in known fashion. For purposes of thisapplication, a processing system includes any system that has aprocessor, such as, for example; a digital signal processor (DSP), amicrocontroller, an application specific integrated circuit (ASIC), or amicroprocessor.

The program code may be implemented in a high level procedural or objectoriented programming language to communicate with a processing system.The program code may also be implemented in assembly or machinelanguage, if desired. In fact, the mechanisms described herein are notlimited in scope to any particular programming language. In any case,the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor.

Such machine-readable storage media may include, without limitation,non-transitory, tangible arrangements of articles manufactured or formedby a machine or device, including storage media such as hard disks, anyother type of disk including floppy disks, optical disks, compact diskread-only memories (CD-ROMs), compact disk rewritable's (CD-RWs), andmagneto-optical disks, semiconductor devices such as read-only memories(ROMs), random access memories (RAMs) such as dynamic random accessmemories (DRAMs), static random access memories (SRAMs), erasableprogrammable read-only memories (EPROMs), flash memories, electricallyerasable programmable read-only memories (EEPROMs), phase change memory(PCM), magnetic or optical cards, or any other type of media suitablefor storing electronic instructions.

Accordingly, embodiments of the invention also include non-transitory,tangible machine-readable media containing instructions or containingdesign data, such as Hardware Description Language (HDL), which definesstructures, circuits, apparatuses, processors and/or system featuresdescribed herein. Such embodiments may also be referred to as programproducts.

Emulation (Including Binary Translation, Code Morphing, Etc.)

In some cases, an instruction converter may be used to convert aninstruction from a source instruction set to a target instruction set.For example, the instruction converter may translate (e.g., using staticbinary translation, dynamic binary translation including dynamiccompilation), morph, emulate, or otherwise convert an instruction to oneor more other instructions to be processed by the core. The instructionconverter may be implemented in software, hardware, firmware, or acombination thereof. The instruction converter may be on processor, offprocessor, or part on and part off processor.

FIG. 31 is a block diagram contrasting the use of a software instructionconverter to convert binary instructions in a source instruction set tobinary instructions in a target instruction set according to embodimentsof the invention. In the illustrated embodiment, the instructionconverter is a software instruction converter, although alternativelythe instruction converter may be implemented in software, firmware,hardware, or various combinations thereof. FIG. 31 shows a program in ahigh level language 3102 may be compiled using an x86 compiler 3104 togenerate x86 binary code 3106 that may be natively executed by aprocessor with at least one x86 instruction set core 3116. The processorwith at least one x86 instruction set core 3116 represents any processorthat can perform substantially the same functions as an Intel processorwith at least one x86 instruction set core by compatibly executing orotherwise processing (1) a substantial portion of the instruction set ofthe Intel x86 instruction set core or (2) object code versions ofapplications or other software targeted to run on an Intel processorwith at least one x86 instruction set core, in order to achievesubstantially the same result as an Intel processor with at least onex86 instruction set core. The x86 compiler 3104 represents a compilerthat is operable to generate x86 binary code 3106 (e.g., object code)that can, with or without additional linkage processing, be executed onthe processor with at least one x86 instruction set core 3116.Similarly, FIG. 31 shows the program in the high level language 3102 maybe compiled using an alternative instruction set compiler 3108 togenerate alternative instruction set binary code 3110 that may benatively executed by a processor without at least one x86 instructionset core 3114 (e.g., a processor with cores that execute the MIPSinstruction set of MIPS Technologies of Sunnyvale, Calif. and/or thatexecute the ARM instruction set of ARM Holdings of Sunnyvale, Calif.).The instruction converter 3112 is used to convert the x86 binary code3106 into code that may be natively executed by the processor without anx86 instruction set core 3114. This converted code is not likely to bethe same as the alternative instruction set binary code 3110 because aninstruction converter capable of this is difficult to make; however, theconverted code will accomplish the general operation and be made up ofinstructions from the alternative instruction set. Thus, the instructionconverter 3112 represents software, firmware, hardware, or a combinationthereof that, through emulation, simulation or any other process, allowsa processor or other electronic device that does not have an x86instruction set processor or core to execute the x86 binary code 3106.

While the sequences of numbers disclosed herein are useful for controlindexes, their use is not limited to control indexes. They may also beused for other purposes (e.g., as input to other instructions oralgorithms). In other embodiments, sequences of other numbers ofintegers (e.g., 6, 12, 20, 24, 128, etc.) may be stored.

The methods shown in the block flow diagrams herein may be performed bygeneral-purpose processors, special-purpose processors (e.g., a graphicsprocessors or a digital signal processors), or other types of digitallogic devices or instruction processing apparatus. In variousembodiments, the instructions may be received at the instructionprocessing apparatus, the processor, or a portion thereof (e.g., adecoder, instruction converter, etc.). In various aspects, theinstruction may be received at the processor from an off-processorsource (e.g., from a main memory, a disc, or a bus/interconnect), orfrom an on-processor source (e.g., from an instruction cache,instruction fetch unit, etc.). In some embodiments, the methods may beperformed by the processor of FIG. 1 and/or the instruction processingapparatus of FIG. 4. Alternatively, the methods may be performed bydifferent embodiments of processors and/or instruction processingapparatus. Moreover, the processor of FIG. 1 and/or the instructionprocessing apparatus of FIG. 4 may perform operations and methods thatare either the same as, similar to, or different than those of themethods shown in the block flow diagrams.

The methods shown in the block flow diagrams herein describe operationsthat are visible from outside a processor or instruction processingapparatus (e.g., visible from a software perspective). For example, theinstruction is provided to the processor and a result is stored in anarchitecturally visible storage location in response to the instruction.In other embodiments, any of these methods may optionally include one ormore other operations occurring internally within the processor orinstruction processing apparatus. By way of example, the instructionsmay be fetched, the instructions may be decoded or otherwise convertedinto one or more other instructions or control signals, execution unitsmay be enabled to perform the operations according to the instructions,microarchitectural operations to implement the operations of theinstructions may be performed (e.g., sequences of integers may becalculated or accessed from a non-architecturally visible storagelocation of an on-die ROM), etc.

The terms “coupled” and “connected,” along with their derivatives, maybe used herein. It should be understood that these terms are notintended as synonyms for each other. Rather, in particular embodiments,“connected” may be used to indicate that two or more elements are indirect physical or electrical contact with each other. “Coupled” maymean that two or more elements are in direct physical or electricalcontact. However, “coupled” may also mean that two or more elements arenot in direct contact with each other, but yet still co-operate orinteract with each other. For example, an execution unit may be coupledwith a register through one or more intervening components. In thefigures, arrows are used to show couplings.

In the description above, for the purposes of explanation, numerousspecific details have been set forth in order to provide a thoroughunderstanding of the embodiments of the invention. It will be apparenthowever, to one skilled in the art, that one or more other embodimentsmay be practiced without some of these specific details. The particularembodiments described are not provided to limit the invention but toillustrate it. The scope of the invention is not to be determined by thespecific examples provided above but only by the claims below. In otherinstances, well-known circuits, structures, devices, and operations havebeen shown in block diagram form or without detail in order to avoidobscuring the understanding of the description.

Various operations and methods have been described. Some of the methodshave been described in a basic form in the flow diagrams, but operationsmay optionally be added to and/or removed from the methods. In addition,a particular order of the operations may have been described, accordingto example embodiments, it is to be understood that that particularorder is exemplary. Alternate embodiments may optionally perform theoperations in different order, combine certain operations, overlapcertain operations, etc.

Certain operations may be performed by hardware components, or may beembodied in machine-executable or circuit-executable instructions, thatmay be used to cause, or at least result in, a circuit or hardwareprogrammed with the instructions performing the operations. The circuitmay include a general-purpose or special-purpose processor, or logiccircuit, to name just a few examples. The operations may also optionallybe performed by a combination of hardware and software. An executionunit and/or a processor may include specific or particular circuitry orother logic responsive to instructions, microinstructions, or one ormore control signals, derived from a machine instruction to performcertain operations.

It should also be appreciated that reference throughout thisspecification to “one embodiment”, “an embodiment”, or “one or moreembodiments”, for example, means that a particular feature may beincluded in the practice of the invention. Similarly, it should beappreciated that in the description various features are sometimesgrouped together in a single embodiment, Figure, or description thereoffor the purpose of streamlining the disclosure and aiding in theunderstanding of various inventive aspects. This method of disclosure,however, is not to be interpreted as reflecting an intention that theinvention requires more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive aspects maylie in less than all features of a single disclosed embodiment. Thus,the claims following the Detailed Description are hereby expresslyincorporated into this Detailed Description, with each claim standing onits own as a separate embodiment of the invention.

What is claimed is:
 1. A method comprising: receiving an instruction,the instruction indicating an integer stride, indicating an integeroffset, and indicating a destination storage location; and storing aresult in the destination storage location in response to theinstruction, the result including a sequence of at least four integersin numerical order with a smallest one of the at least four integersdiffering from zero by the integer offset and with all integers of thesequence in consecutive positions differing by the integer stride. 2.The method of claim 1, wherein receiving the instruction comprisesreceiving an instruction that explicitly specifies the integer stride.3. The method of claim 1, wherein receiving the instruction comprisesreceiving an instruction that explicitly specifies the integer offset.4. The method of claim 1, wherein receiving the instruction comprisesreceiving an instruction that indicates a sequence of at least fourconsecutive integers in numerical order.
 5. The method of claim 4,wherein storing the result includes storing at least four integers thateach represent a corresponding one of the at least four consecutiveintegers added to the integer offset and multiplied by the integerstride.
 6. The method of claim 1, wherein receiving the instructioncomprises receiving an instruction that, aside from the integer offsetand the integer stride, does not indicate a source operand in anarchitecturally-visible storage location.
 7. The method of claim 1,wherein storing the result comprises storing a sequence of at leasteight integers in the numerical order with all integers of the sequencein consecutive positions differing by the integer stride.
 8. The methodof claim 1, further comprising receiving one of a permute instruction, agather instruction, and a scatter instruction, which indicates theresult in the destination storage location.
 9. The method of claim 1,wherein the integer stride is at least two.
 10. An apparatus comprising:a destination storage location; and an execution unit coupled with thedestination storage location, the execution unit, in response to aninstruction indicating an integer stride, indicating an integer offset,and indicating a destination storage location, to store a result in thedestination storage location, the result including a sequence of atleast four integers in numerical order with a smallest one of the atleast four integers differing from zero by the integer offset and withall integers of the sequence in consecutive positions differing by theinteger stride.
 11. The apparatus of claim 10, wherein the instruction,aside from the integer offset and the integer stride, is not to indicatea source operand in an architecturally-visible storage location.
 12. Theapparatus of claim 10, wherein the instruction is to further indicate asequence of at least four consecutive integers in numerical order. 13.The apparatus of claim 12, wherein the execution unit, in response tothe instruction, is to store at least four integers of the result thateach represent a corresponding one of the at least four consecutiveintegers added to the integer offset and multiplied by the integerstride.
 14. The apparatus of claim 10, wherein the instructionexplicitly specifies the integer stride.
 15. The apparatus of claim 10,wherein the instruction explicitly specifies the integer offset.
 16. Theapparatus of claim 10, wherein the execution unit, in response to theinstruction, is to store the result including a sequence of at leasteight integers in the numerical order with all integers in consecutivepositions differing by the integer stride.
 17. The apparatus of claim16, wherein the execution unit, in response to the instruction, is tostore the result including a sequence of at least sixteen integers inthe numerical order with all integers in consecutive positions differingby the integer stride.
 18. The apparatus of claim 10, wherein theinstruction comprises a control indexes generation instruction for oneof a permute instruction, a shuffle instruction, a gather instruction,and a scatter instruction.
 19. A system comprising: an interconnect; aprocessor coupled with the interconnect, the processor including adestination register, the processor, in response to an instructionindicating an integer stride, indicating an integer offset, andindicating the destination register, to store a result in thedestination register, the result including a sequence of at least fourintegers in numerical order with a smallest one of the at least fourintegers differing from zero by the integer offset and with all integersof the sequence in consecutive positions differing by the integerstride; and a dynamic random access memory (DRAM) coupled with theinterconnect.
 20. The system of claim 19, wherein the instruction is tofurther indicate a sequence of at least four consecutive integers innumerical order.
 21. The system of claim 19, wherein the instruction,aside from the integer offset and the integer stride, is not to indicatea source operand in an architecturally-visible storage location.
 22. Anarticle of manufacture comprising: a machine-readable storage mediumincluding one or more solid storage materials, the machine-readablestorage medium storing an instruction, the instruction to indicate aninteger stride, an integer offset, and a destination storage location,and the instruction, if executed by a machine, to cause the machine toperform operations comprising: storing a result in the destinationstorage location, the result including a sequence of at least fourintegers in numerical order with a smallest one of the at least fourintegers differing from zero by the integer offset and with all integersof the sequence in consecutive positions differing by the integerstride.
 23. The article of claim 22, wherein the instruction is tofurther indicate a sequence of at least four consecutive integers innumerical order.
 24. The article of claim 22, wherein the instruction,aside from the integer offset and the integer stride, is not to indicatea source operand in an architecturally-visible storage location.
 25. Thearticle of claim 22, wherein the machine-readable storage medium furtherstores an instruction selected from a permute instruction, a shuffleinstruction, a scatter instruction, and a gather instruction, whichindicates the result in the destination storage location as a sourceoperand.